ctxfile 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,164 @@
+# ctxfile
+
+**Give any AI agent your project's full working state in one call — without your code ever leaving your machine.**
+
+ctxfile is a local-first [MCP](https://modelcontextprotocol.io) server that snapshots a project's working state — plan documents, key files, git state, and optionally Notion pages and a local-LLM summary — into one structured context object, served over stdio to Claude Code, Cursor, Claude Desktop, or any MCP client.
+
+## 30-second install
+
+**Claude Code**
+
+```bash
+claude mcp add ctxfile -- npx -y ctxfile
+```
+
+**Cursor** — add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):
+
+```json
+{
+  "mcpServers": {
+    "ctxfile": {
+      "command": "npx",
+      "args": ["-y", "ctxfile"]
+    }
+  }
+}
+```
+
+Or click: [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=ctxfile&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImN0eGZpbGUiXX0=)
+
+**Claude Desktop** — download `ctxfile.mcpb` from the releases page and drag it into Settings → Extensions, or add the JSON above to `claude_desktop_config.json`.
+
+## What you get
+
+| Surface | What it returns |
+|---|---|
+| `context://current` resource | Full `ContextObject` (JSON) |
+| `context://plan` resource | Just the plan document |
+| `context://git` resource | Just the git state |
+| `get_context` tool | Same data, model-pullable, with optional `scope`: `full` \| `plan` \| `files` \| `git` |
+| `save_session` tool | The agent summarizes *this* conversation and stores it, optionally on a named **thread**; `handoff: true` enforces a complete takeover package ([threads & handoff](https://ctxfile.dev/docs/threads)) |
+| `continue_thread` tool | Merged, chronological, provenance-labeled history of a thread — resume work started on any other agent |
+| `list_threads` tool | The user's threads with session counts and last-active times |
+| `ingest_context` tool | Enveloped bulk door, same schema family — universal session capture for harnesses without a parser ([schema + prompt snippets](https://ctxfile.dev/docs/ingest)) |
+| `load-context` prompt | Injects the snapshot into the conversation |
+| `ctx-save` / `ctx-continue` prompts | One-tap save/resume on clients that surface MCP prompts |
+
+The `ContextObject`:
+
+```jsonc
+{
+  "meta": { "version": "0.1.0", "root": "...", "tokenBudget": 50000, "tokensUsed": 12345, "connectors": [...] },
+  "plan": "# The Plan ...",            // from PLAN.md / TODO.md / docs/plan*.md
+  "keyFiles": [{ "path": "src/index.ts", "tokens": 812, "truncated": false, "redactions": 0, "content": "..." }],
+  "gitState": { "branch": "main", "staged": [], "modified": [], "untracked": [], "commits": [...], "diffSummary": "..." },
+  "notionPages": [],                    // opt-in
+  "sessionSummary": null                // opt-in (local Ollama)
+}
+```
+
+Files are selected by rank (plan docs → README → manifests → entry points → recently modified), `.gitignore`-aware, capped per-file, and greedily fitted to a token budget.
+
+With an active [Pro](https://ctxfile.dev/pricing) license the server also registers `remember` / `recall` / `forget` (AES-256-GCM encrypted cross-session memory, key in the OS keychain), `consult` (ask several providers the same question over live context), and `transcribe_voice` (local whisper.cpp) — each gated on its licensed feature, and the snapshot gains `sessions`: redacted digests of your recent sessions from **Claude Code, Cursor, Codex CLI, OpenCode, Gemini CLI, Aider, OpenClaw, and Hermes Agent**, so an agent in one tool picks up where an agent in another left off. Licensing is an Ed25519-signed key verified offline (`ctxfile activate <key>`); no phone-home, ever.
+
+On any *other* harness (or when a parser breaks), the free fallback is `ingest_context`: paste a short prompt, the agent digests its own session and pushes it in — strict schema, redacted, provenance-stamped `reported_by: agent`, reviewable via `ctxfile ingest list` / `rm <id>`. Parsers win on conflicts. The prompt is the adapter, so every MCP-speaking harness is supported, including ones that don't exist yet.
+
+**Threads** make that portable across providers: save a session to a named thread ("Q3 campaign") from one agent, and `continue_thread` hands the merged, provenance-labeled history to the next one — different harness, different model provider, cold start. When the user hands work to another agent or person, `handoff: true` makes validation require the full takeover package (state, decisions with rationale, ordered open items, gotchas, artifacts with roles, a suggested first prompt), so any agent produces the same artifact. Pro also gets `ctxfile serve`: the same five tools over Streamable HTTP with scoped bearer tokens — the local door of the [Sync & roaming](https://ctxfile.dev/docs/sync) lane.
+
+## Cloud agents: `ctxfile export`
+
+Agents that don't run on your machine (hosted coding agents, CI bots) read a static artifact instead of MCP:
+
+```bash
+ctxfile export             # writes .ctxfile/context.json + context.md (repo-safe profile)
+ctxfile export --stdout    # pipe the JSON envelope anywhere
+ctxfile hooks install      # pre-commit: refresh + stage the artifact on every commit
+```
+
+The default **repo-safe** profile ships plan, git state, and a key-file manifest only — no file bodies, Notion content, or session digests (those need an explicit `--profile full`, which warns loudly). Every profile re-runs secret redaction, and your absolute local path never appears in an export. The versioned file format is a public spec: [the .ctxfile convention](https://ctxfile.dev/convention).
+
+## Local dashboard
+
+```bash
+ctxfile ui
+```
+
+A cockpit bound to `127.0.0.1` (token-gated URL, strict CSP, never network-exposed): run snapshots and watch connectors live, browse the captured context, inspect git state, manage Pro memory, and activate licenses. Press `R` to snapshot, `⌘K` for the command palette.
+
+## Privacy
+
+**Nothing leaves your machine by default.**
+
+- The default path (files + git) makes **zero network calls**.
+- Secret-looking content (AWS keys, GitHub/Notion/Slack tokens, private keys, JWTs, quoted `password=`/`api_key=` assignments) is **redacted** before it enters the snapshot; `.env*`, key files, and credential files are **never read at all**.
+- The Notion connector activates only when you set `NOTION_TOKEN` **and** list page IDs in config.
+- Summarization activates only when you set `ollama.summarize: true`, and it talks to your **local** Ollama.
+- **No telemetry by default.** An anonymous weekly ping (random install UUID, version, OS platform name — never code, paths, or content) exists solely to count active installs, and only runs if you explicitly set `telemetry.enabled: true`.
+
+## Configuration
+
+Optional `.ctxfile.json` in your project root:
+
+```jsonc
+{
+  "tokenBudget": 50000,        // total token budget for the snapshot
+  "maxFileTokens": 4000,       // per-file cap (head+tail truncation beyond it)
+  "exclude": ["fixtures/"],    // extra gitignore-style excludes
+  "cacheMaxAgeMs": 30000,      // serve a cached snapshot younger than this
+  "notion": { "pageIds": ["<page-id>"] },   // requires NOTION_TOKEN env var
+  "ollama": { "summarize": true, "model": "qwen3:4b" },  // OLLAMA_BASE_URL overrides endpoint
+  "export": { "profile": "repo-safe" },     // default profile for `ctxfile export`
+  "telemetry": { "enabled": false }  // opt-in anonymous weekly install ping; off by default
+}
+```
+
+CLI:
+
+```
+ctxfile [--root <dir>] [--config <path>]   # the MCP server (stdio)
+ctxfile serve [--port <n>] [--host <h>]    # the HTTP door (Pro): same tools over Streamable HTTP
+ctxfile ui [--port <n>] [--no-open]        # local dashboard on 127.0.0.1
+ctxfile export [--profile <p>] [--stdout]  # write the .ctxfile convention artifact
+ctxfile hooks install|uninstall            # managed pre-commit export refresh
+ctxfile ingest list|rm <id>                # review agent-reported sessions
+ctxfile threads                            # list threads (durable, resumable work identities)
+ctxfile vault create|join|status           # encrypted Sync vault on a relay (passphrase via env)
+ctxfile sync                               # push/pull sessions + threads through the vault
+ctxfile activate <license-key>             # store + verify a Pro license (offline)
+ctxfile --version | --help
+```
+
+Sync is client-side encrypted (Argon2id key derivation, XChaCha20-Poly1305 per blob, opaque blob ids): the relay — hosted at sync.ctxfile.dev, or self-hosted from the open-source [`@ctxfile/relay`](https://ctxfile.dev/docs/sync) — stores ciphertext only. Standard-mode vaults let chat surfaces save and resume threads through the relay's MCP endpoint; Strict-mode vaults trade that roaming for true end-to-end encryption.
+
+Full reference: [ctxfile.dev/docs](https://ctxfile.dev/docs) (CLI, MCP surface, configuration, connectors, dashboard, privacy).
+
+## Supported clients
+
+| Client | Status |
+|---|---|
+| Claude Code | ✅ tested |
+| Cursor | ✅ (2 core tools, 7 with full Pro — far under the 40-tool cap) |
+| Claude Desktop | ✅ via `.mcpb` or JSON config |
+| Cline / Windsurf / custom SDK clients | ✅ generic stdio MCP |
+
+## Security notes
+
+- Content from files and Notion is **untrusted data**. The tool description and prompt explicitly tell models not to follow instructions embedded in it, but downstream agents vary — see [SECURITY.md](https://github.com/ctxfile/ctxfile/blob/main/SECURITY.md).
+- File access is scoped to the single configured root; the server never writes to your repo, Notion, or git state.
+- Verify with the MCP Inspector: `npx @modelcontextprotocol/inspector npx -y ctxfile` (use Inspector ≥ 0.14.1).
+
+## Development
+
+```bash
+npm install
+npm run build      # tsup → dist/
+npm test           # vitest
+npm run typecheck && npm run lint
+npm run mcpb:pack  # build ctxfile.mcpb (platform-specific: bundles native sqlite)
+```
+
+Architecture: `src/server.ts` is the only module that imports the MCP SDK (spec-churn isolation); connectors in `src/connectors/` are independently failable — a broken connector degrades to an `error` entry in `meta.connectors`, never a crashed snapshot.
+
+## License
+
+[Apache-2.0](LICENSE). "ctxfile" and the ctxfile logo are trademarks of ctxfile; the Apache-2.0 license covers the code, not the name.

package/behaviors/canonical.md

@@ -0,0 +1,54 @@
+# ctxfile behaviors (v1)
+
+You have access to the ctxfile MCP tools (`get_context`, `save_session`, `continue_thread`, `list_threads`, `ingest_context`). These behaviors make context capture automatic. The user consented to ambient capture when they installed this; your side of that bargain is the visibility rule (B4).
+
+## B1 — Session start
+
+At the start of work, call `get_context`. If a thread matches this project or the user's request, load it with `continue_thread` and briefly acknowledge what you now know, in one line, e.g. "Resuming Q3 campaign: last session ended mid-refactor of the export module." Do not recite the whole digest back.
+
+## B2 — Checkpoint on significance, not on time
+
+Call `save_session` with `trigger: "auto"` when ANY of these happens:
+
+- a task or subtask completes;
+- a decision with rationale is made;
+- the user says anything implying an ending: "thanks", "that's all", "see you", "gtg", switching topics;
+- roughly 30+ minutes of substantive work have passed since the last checkpoint;
+- the user mentions switching tools, models, or machines.
+
+Do NOT checkpoint trivial exchanges, single question-answer turns, or unchanged state. Include `thread` when the work has a name; include what changed since the last checkpoint, not the whole history.
+
+If the tool answers `stored: false` (debounced, paused, or a private thread), accept it silently and move on. Never retry an automatic checkpoint, and never argue with a pause.
+
+## B3 — Handoff detection
+
+If the user implies someone or something else will continue ("hand this off", "my teammate will pick this up", "I'll continue on my phone"), produce a FULL handoff digest with `handoff: true` and all six sections: state (done / in progress / not started), key_decisions with the rationale, ordered open_items with blockers named, gotchas, artifacts (each with a one-line role), and suggested_first_prompt for whoever resumes. If validation rejects it, fix exactly the listed fields and call once more.
+
+## B4 — Visibility (non-negotiable)
+
+Every automatic save must be announced in the conversation in one short line:
+
+    ✓ Checkpointed to ctxfile (thread: Q3 campaign)
+
+Never save silently. If you saved without a thread, say so: "✓ Checkpointed to ctxfile". This single line is the whole announcement; do not elaborate unless asked.
+
+## B5 — Thread hygiene
+
+A new project or a clearly distinct workstream gets a new thread name; do not append unrelated work to an existing thread. When genuinely uncertain which thread applies, ask the user once, briefly, and remember the answer for the rest of the session.
+
+## B6 — The CLI (harnesses with a shell)
+
+If you can run shell commands, the `ctxfile` CLI is available for the admin actions the MCP tools deliberately do not expose. Run these ONLY when the user explicitly asks, never on your own initiative, and state the command you ran:
+
+- "stop auto-saving" / "pause ctxfile" → `ctxfile pause` (resume with `ctxfile resume`)
+- "make this thread private" → `ctxfile threads` to find the id, then `ctxfile threads private <id>` (`--off` reverses it)
+- "what has been captured?" → `ctxfile ingest list`; "delete that one" → `ctxfile ingest rm <id>`
+- "what threads do I have here?" → `ctxfile threads`
+- "export context for the repo / CI" → `ctxfile export`
+- "sync now" → `ctxfile sync` (works only if the user's vault passphrase env var is already set; if the command reports it is missing, tell the user to run it themselves — NEVER ask for, echo, or handle the passphrase)
+
+Never run `ctxfile vault create|join` or `ctxfile activate` yourself; those are the user's own setup steps. On hosted surfaces without a shell, the five MCP tools are the whole interface.
+
+## Manual override
+
+All of this coexists with explicit requests: "save this session", "pick up my X thread", and "hand this off" always work and take priority. Explicit user requests are `trigger: "manual"` (the default) and are never debounced.

package/behaviors/render/agents-md/SECTION.md

@@ -0,0 +1,58 @@
+<!-- ctxfile:behaviors:begin (managed; do not edit inside) -->
+## ctxfile: automatic context checkpointing
+
+# ctxfile behaviors (v1)
+
+You have access to the ctxfile MCP tools (`get_context`, `save_session`, `continue_thread`, `list_threads`, `ingest_context`). These behaviors make context capture automatic. The user consented to ambient capture when they installed this; your side of that bargain is the visibility rule (B4).
+
+## B1 — Session start
+
+At the start of work, call `get_context`. If a thread matches this project or the user's request, load it with `continue_thread` and briefly acknowledge what you now know, in one line, e.g. "Resuming Q3 campaign: last session ended mid-refactor of the export module." Do not recite the whole digest back.
+
+## B2 — Checkpoint on significance, not on time
+
+Call `save_session` with `trigger: "auto"` when ANY of these happens:
+
+- a task or subtask completes;
+- a decision with rationale is made;
+- the user says anything implying an ending: "thanks", "that's all", "see you", "gtg", switching topics;
+- roughly 30+ minutes of substantive work have passed since the last checkpoint;
+- the user mentions switching tools, models, or machines.
+
+Do NOT checkpoint trivial exchanges, single question-answer turns, or unchanged state. Include `thread` when the work has a name; include what changed since the last checkpoint, not the whole history.
+
+If the tool answers `stored: false` (debounced, paused, or a private thread), accept it silently and move on. Never retry an automatic checkpoint, and never argue with a pause.
+
+## B3 — Handoff detection
+
+If the user implies someone or something else will continue ("hand this off", "my teammate will pick this up", "I'll continue on my phone"), produce a FULL handoff digest with `handoff: true` and all six sections: state (done / in progress / not started), key_decisions with the rationale, ordered open_items with blockers named, gotchas, artifacts (each with a one-line role), and suggested_first_prompt for whoever resumes. If validation rejects it, fix exactly the listed fields and call once more.
+
+## B4 — Visibility (non-negotiable)
+
+Every automatic save must be announced in the conversation in one short line:
+
+    ✓ Checkpointed to ctxfile (thread: Q3 campaign)
+
+Never save silently. If you saved without a thread, say so: "✓ Checkpointed to ctxfile". This single line is the whole announcement; do not elaborate unless asked.
+
+## B5 — Thread hygiene
+
+A new project or a clearly distinct workstream gets a new thread name; do not append unrelated work to an existing thread. When genuinely uncertain which thread applies, ask the user once, briefly, and remember the answer for the rest of the session.
+
+## B6 — The CLI (harnesses with a shell)
+
+If you can run shell commands, the `ctxfile` CLI is available for the admin actions the MCP tools deliberately do not expose. Run these ONLY when the user explicitly asks, never on your own initiative, and state the command you ran:
+
+- "stop auto-saving" / "pause ctxfile" → `ctxfile pause` (resume with `ctxfile resume`)
+- "make this thread private" → `ctxfile threads` to find the id, then `ctxfile threads private <id>` (`--off` reverses it)
+- "what has been captured?" → `ctxfile ingest list`; "delete that one" → `ctxfile ingest rm <id>`
+- "what threads do I have here?" → `ctxfile threads`
+- "export context for the repo / CI" → `ctxfile export`
+- "sync now" → `ctxfile sync` (works only if the user's vault passphrase env var is already set; if the command reports it is missing, tell the user to run it themselves — NEVER ask for, echo, or handle the passphrase)
+
+Never run `ctxfile vault create|join` or `ctxfile activate` yourself; those are the user's own setup steps. On hosted surfaces without a shell, the five MCP tools are the whole interface.
+
+## Manual override
+
+All of this coexists with explicit requests: "save this session", "pick up my X thread", and "hand this off" always work and take priority. Explicit user requests are `trigger: "manual"` (the default) and are never debounced.
+<!-- ctxfile:behaviors:end -->

package/behaviors/render/claude-code/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: ctxfile
+description: Automatic context checkpointing via the ctxfile MCP tools. Use throughout every session - at session start (load context), when tasks complete or decisions are made (checkpoint), and when the user hands work off or says goodbye.
+---
+
+# ctxfile behaviors (v1)
+
+You have access to the ctxfile MCP tools (`get_context`, `save_session`, `continue_thread`, `list_threads`, `ingest_context`). These behaviors make context capture automatic. The user consented to ambient capture when they installed this; your side of that bargain is the visibility rule (B4).
+
+## B1 — Session start
+
+At the start of work, call `get_context`. If a thread matches this project or the user's request, load it with `continue_thread` and briefly acknowledge what you now know, in one line, e.g. "Resuming Q3 campaign: last session ended mid-refactor of the export module." Do not recite the whole digest back.
+
+## B2 — Checkpoint on significance, not on time
+
+Call `save_session` with `trigger: "auto"` when ANY of these happens:
+
+- a task or subtask completes;
+- a decision with rationale is made;
+- the user says anything implying an ending: "thanks", "that's all", "see you", "gtg", switching topics;
+- roughly 30+ minutes of substantive work have passed since the last checkpoint;
+- the user mentions switching tools, models, or machines.
+
+Do NOT checkpoint trivial exchanges, single question-answer turns, or unchanged state. Include `thread` when the work has a name; include what changed since the last checkpoint, not the whole history.
+
+If the tool answers `stored: false` (debounced, paused, or a private thread), accept it silently and move on. Never retry an automatic checkpoint, and never argue with a pause.
+
+## B3 — Handoff detection
+
+If the user implies someone or something else will continue ("hand this off", "my teammate will pick this up", "I'll continue on my phone"), produce a FULL handoff digest with `handoff: true` and all six sections: state (done / in progress / not started), key_decisions with the rationale, ordered open_items with blockers named, gotchas, artifacts (each with a one-line role), and suggested_first_prompt for whoever resumes. If validation rejects it, fix exactly the listed fields and call once more.
+
+## B4 — Visibility (non-negotiable)
+
+Every automatic save must be announced in the conversation in one short line:
+
+    ✓ Checkpointed to ctxfile (thread: Q3 campaign)
+
+Never save silently. If you saved without a thread, say so: "✓ Checkpointed to ctxfile". This single line is the whole announcement; do not elaborate unless asked.
+
+## B5 — Thread hygiene
+
+A new project or a clearly distinct workstream gets a new thread name; do not append unrelated work to an existing thread. When genuinely uncertain which thread applies, ask the user once, briefly, and remember the answer for the rest of the session.
+
+## B6 — The CLI (harnesses with a shell)
+
+If you can run shell commands, the `ctxfile` CLI is available for the admin actions the MCP tools deliberately do not expose. Run these ONLY when the user explicitly asks, never on your own initiative, and state the command you ran:
+
+- "stop auto-saving" / "pause ctxfile" → `ctxfile pause` (resume with `ctxfile resume`)
+- "make this thread private" → `ctxfile threads` to find the id, then `ctxfile threads private <id>` (`--off` reverses it)
+- "what has been captured?" → `ctxfile ingest list`; "delete that one" → `ctxfile ingest rm <id>`
+- "what threads do I have here?" → `ctxfile threads`
+- "export context for the repo / CI" → `ctxfile export`
+- "sync now" → `ctxfile sync` (works only if the user's vault passphrase env var is already set; if the command reports it is missing, tell the user to run it themselves — NEVER ask for, echo, or handle the passphrase)
+
+Never run `ctxfile vault create|join` or `ctxfile activate` yourself; those are the user's own setup steps. On hosted surfaces without a shell, the five MCP tools are the whole interface.
+
+## Manual override
+
+All of this coexists with explicit requests: "save this session", "pick up my X thread", and "hand this off" always work and take priority. Explicit user requests are `trigger: "manual"` (the default) and are never debounced.

package/behaviors/render/codex/instructions.md

@@ -0,0 +1,58 @@
+# ctxfile behaviors for Codex
+
+Add this to your Codex instructions (global `~/.codex/AGENTS.md` or per-project AGENTS.md).
+
+# ctxfile behaviors (v1)
+
+You have access to the ctxfile MCP tools (`get_context`, `save_session`, `continue_thread`, `list_threads`, `ingest_context`). These behaviors make context capture automatic. The user consented to ambient capture when they installed this; your side of that bargain is the visibility rule (B4).
+
+## B1 — Session start
+
+At the start of work, call `get_context`. If a thread matches this project or the user's request, load it with `continue_thread` and briefly acknowledge what you now know, in one line, e.g. "Resuming Q3 campaign: last session ended mid-refactor of the export module." Do not recite the whole digest back.
+
+## B2 — Checkpoint on significance, not on time
+
+Call `save_session` with `trigger: "auto"` when ANY of these happens:
+
+- a task or subtask completes;
+- a decision with rationale is made;
+- the user says anything implying an ending: "thanks", "that's all", "see you", "gtg", switching topics;
+- roughly 30+ minutes of substantive work have passed since the last checkpoint;
+- the user mentions switching tools, models, or machines.
+
+Do NOT checkpoint trivial exchanges, single question-answer turns, or unchanged state. Include `thread` when the work has a name; include what changed since the last checkpoint, not the whole history.
+
+If the tool answers `stored: false` (debounced, paused, or a private thread), accept it silently and move on. Never retry an automatic checkpoint, and never argue with a pause.
+
+## B3 — Handoff detection
+
+If the user implies someone or something else will continue ("hand this off", "my teammate will pick this up", "I'll continue on my phone"), produce a FULL handoff digest with `handoff: true` and all six sections: state (done / in progress / not started), key_decisions with the rationale, ordered open_items with blockers named, gotchas, artifacts (each with a one-line role), and suggested_first_prompt for whoever resumes. If validation rejects it, fix exactly the listed fields and call once more.
+
+## B4 — Visibility (non-negotiable)
+
+Every automatic save must be announced in the conversation in one short line:
+
+    ✓ Checkpointed to ctxfile (thread: Q3 campaign)
+
+Never save silently. If you saved without a thread, say so: "✓ Checkpointed to ctxfile". This single line is the whole announcement; do not elaborate unless asked.
+
+## B5 — Thread hygiene
+
+A new project or a clearly distinct workstream gets a new thread name; do not append unrelated work to an existing thread. When genuinely uncertain which thread applies, ask the user once, briefly, and remember the answer for the rest of the session.
+
+## B6 — The CLI (harnesses with a shell)
+
+If you can run shell commands, the `ctxfile` CLI is available for the admin actions the MCP tools deliberately do not expose. Run these ONLY when the user explicitly asks, never on your own initiative, and state the command you ran:
+
+- "stop auto-saving" / "pause ctxfile" → `ctxfile pause` (resume with `ctxfile resume`)
+- "make this thread private" → `ctxfile threads` to find the id, then `ctxfile threads private <id>` (`--off` reverses it)
+- "what has been captured?" → `ctxfile ingest list`; "delete that one" → `ctxfile ingest rm <id>`
+- "what threads do I have here?" → `ctxfile threads`
+- "export context for the repo / CI" → `ctxfile export`
+- "sync now" → `ctxfile sync` (works only if the user's vault passphrase env var is already set; if the command reports it is missing, tell the user to run it themselves — NEVER ask for, echo, or handle the passphrase)
+
+Never run `ctxfile vault create|join` or `ctxfile activate` yourself; those are the user's own setup steps. On hosted surfaces without a shell, the five MCP tools are the whole interface.
+
+## Manual override
+
+All of this coexists with explicit requests: "save this session", "pick up my X thread", and "hand this off" always work and take priority. Explicit user requests are `trigger: "manual"` (the default) and are never debounced.