Integrations
0ctx separates ingestion (capturing context) from retrieval (providing context to agents). Both happen automatically after enable.
Ingestion
Ingestion is deterministic. It comes from:
- Repo-installed hooks
- Session-start integrations
- Transcript and archive readers
Integrations feed the local daemon. The daemon remains the source of truth for the local product path.
Retrieval
Retrieval for supported agents goes through MCP and daemon-backed context packs. The intended user experience is:
- Enable once
- Use the agent normally
- Get the right workstream context automatically
GA integrations
Claude Code
| Capability | Mechanism |
|---|---|
| Capture | Stop, SubagentStop |
| Startup context | SessionStart |
| Retrieval | MCP + daemon-backed context pack |
Factory / Droid
| Capability | Mechanism |
|---|---|
| Capture | Stop, SubagentStop |
| Startup context | SessionStart |
| Retrieval | Daemon-backed context pack injected on session start |
Antigravity
| Capability | Mechanism |
|---|---|
| Capture | Managed repo hook install |
| Startup context | Session-start integration path |
| Retrieval | Daemon-backed context pack |
Preview integrations
Preview integrations are supported only when explicitly opted into. They are intentionally outside the normal product path.
- Codex
- Cursor
- Windsurf
Product rule
Users should not need to think about contextId, MCP setup details, hook event internals, or transcript plumbing. The normal path is cd <repo> && 0ctx enable.