context-canopy
AGENTS.md3 starsChanged 3 months agoMITView on GitHub
This repository is the public ContextCanopy distribution. It is not a user's personalized authority. Run checks that match the change. For a repository-wide release change, run: Tests must use temporary copies and must not write to a live personalized Vault. Report untested hosts and remaining migration limits explicitly.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- mcp/AGENTS.mdAGENTS.md
- vault/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- mcp/CLAUDE.mdCLAUDE.md
- vault/CLAUDE.mdCLAUDE.md
- capture-knowledgeSkill
- second-brain-attachSkill
- second-brain-climbSkill
- second-brain-distillSkill
- second-brain-doctorSkill
- second-brain-helpSkill
- second-brain-learnSkill
- second-brain-syncSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Before writing real personal context, have the user choose local-only or private-remote authority.
- Distinctive: line 18
Keep common user context separate from each Agent's role.
- Distinctive: line 29
Run checks that match the change.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ContextCanopy Agent Entry
This repository is the public ContextCanopy distribution. It is not a user's personalized authority.
Route before acting
- For setup or migration, read
README.mdandskills/second-brain-attach/SKILL.md; finish withsecond-brain-doctorin a fresh host session. - For Vault reads or writes, work from
vault/and readvault/AGENTS.mdcompletely before acting. - For MCP code or tests, work from
mcp/and readmcp/AGENTS.mdcompletely before acting. - For documentation changes, keep
README.mdandREADME.zh-CN.mdsemantically aligned. Do not translate code, paths, commands, or compatibility identifiers. - The installable
skills/second-brain-*directories and theirvault/90-System/Personal-AI/SKILLS/mirrors express the same public contract. Update both and verify byte equality; do not let them become competing owners.
Privacy and authority boundary
- Before writing real personal context, have the user choose
local-onlyorprivate-remoteauthority. - The public ContextCanopy remote is distribution-only. Never push a personalized Vault, raw conversations, credentials, private repository URLs, unpublished research, or sensitive evidence to it.
- A
private-remotesetup must use a separate repository whose private visibility and writable identity were verified live. A public fork is not a personal Vault. - Keep common user context separate from each Agent's role. A new Agent should recognize the same person without becoming a clone of another Agent.
Portability claims
- ContextCanopy moves user-owned durable context, Skills, and host projections. It does not move model weights, hidden provider memory, credentials, permissions, or active runtime state.
- Selected accessible conversations and exports can be migrated through the guided Distill workflow. Do not claim a universal one-click provider-memory importer unless one has been implemented and verified.
- Configuration-file presence is not installation proof. Attach and Sync complete only after the target host passes a fresh-session Doctor check.
- Active rule files express the current effective state, not an append-only learning log. Preserve superseded evidence in Git and release history, remove retired behavior from active templates, and verify both the new behavior and the old behavior's exit.
Completion evidence
Run checks that match the change. For a repository-wide release change, run:
npm test
npm run smoke
cd mcp
node --check index.js
node --check lib/vault-writer.js
node --check scripts/stdio-full-vault-smoke.mjs
npm pack --dry-run
npm audit --audit-level=lowTests must use temporary copies and must not write to a live personalized Vault. Report untested hosts and remaining migration limits explicitly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.