cursor / cursor/plugins

continual-learning: support user-owned cadence config and repo denylist

Open
#141 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
8.2k
Forks
751
Avg merge
12h 1m
Merged PRs (30d)
43

Description

Request

Please let the continual-learning plugin read durable user-owned configuration for:

  • cadence: minimum turns and minimum minutes before the stop hook can trigger
  • repo denylist: owners, slugs, and/or path prefixes where the miner should not write AGENTS.md

Current gap

The marketplace stop hook currently carries inline cadence environment variables in hooks/hooks.json. Local users can patch the plugin cache, but that is brittle because marketplace cache refreshes can restore the upstream defaults.

A companion publisher can prevent publishing from denied repos, but it cannot prevent the marketplace miner itself from writing local AGENTS.md in a workspace where the plugin is enabled.

Desired behavior

A stable config source, for example under the user's Cursor config directory, would allow:

  • permanent cadence such as 3 turns / 15 minutes without trial expiry
  • hard repo deny before any local AGENTS.md write
  • no cache patching or generated hook-command rewrites
  • a clear migration path for local governance tools to retire cache projection

Thanks.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the continual-learning plugin and the inline cadence environment variables in hooks/hooks.json, then trace how the marketplace stop hook and miner are configured. Done means a durable user-owned cadence and repo denylist can be honored before any local AGENTS.md write, without cache patching or generated hook-command rewrites.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.