Part of #374
Question
How does a user control what is captured: per project, per session, per connector?
Sub-questions
- Exclusions. By repo path, by glob, or by an explicit include list (allowlist)? The Collection Tier already prefers allowlists (
actions-graph/CONTEXT.md).
- Pause / resume for the current session. Where does that state live, given hook subprocesses read only the config file? A per-session entry in config? A marker file? And how does the agent trigger it from chat?
- Connector selection is currently hardcoded in each plugin's
hooks.json (--connector ... ×3). Should it move to config so users can turn a connector off without editing plugin files?
- Paused vs dropped. When capture is paused, is the Session node still created (so
status can show "paused") or is nothing written?
Part of #374
Question
How does a user control what is captured: per project, per session, per connector?
Sub-questions
actions-graph/CONTEXT.md).hooks.json(--connector ...×3). Should it move to config so users can turn a connector off without editing plugin files?statuscan show "paused") or is nothing written?