llms.txt
# scritty
> scritty is one terminal for every supported AI coding agent, with one
> persistent searchable memory you control. Run Claude Code, OpenAI Codex CLI,
> GitHub Copilot CLI, Gemini CLI, Antigravity CLI, Grok CLI, or Ollama inside
> scritty. It captures attributable turns at the terminal boundary, tags them
> with the provider, and serves the shared corpus through the terminal panel,
> MCP, CLI, browser, and phone.
Website: https://scritty.dev
Public documentation and issues: https://github.com/scritty-org/scritty
Contact: hello@scritty.dev
## What scritty is
- A native terminal emulator for Linux, Windows, and macOS on Apple Silicon.
- A supported-provider capture layer. Unknown CLIs still run normally but are
not auto-captured until a provider entry is added.
- One local corpus across vendors: decisions made in one agent can be searched
by another agent later.
- Local-first by default: SQLite plus an embedded vector/keyword index on the
user's machine, with no captured content or telemetry leaving the machine.
## How capture works
- Provider detection uses process identity, not prompt text: `/proc` on Linux,
`libproc` plus `sysctl(KERN_PROCARGS2)` on macOS, and
`NtQueryInformationProcess`/ToolHelp on Windows.
- Under tmux, scritty resolves the owning client by pty, durably spools each
pane's `%output` / `%extended-output` stream, and replays it through a
per-pane terminal. Two agents in two panes become two conversations.
- Scritty records the output a pane wrote after a prompt scritty submitted. It
does not guess authorship from UI glyphs or strip terminal chrome by
appearance.
- Input scritty did not submit, such as history recall or another client's
`send-keys`, is not attributed to a turn.
- Named loss is visible in the stored exchange. Replies retain rows that scroll
out, including inside scroll regions and the alternate screen; an
application-deleted line is treated as an edit, not capture loss.
## Search and interfaces
- Hybrid search combines offline dual ONNX embeddings with keyword ranking via
Reciprocal Rank Fusion.
- Vector backends: cosynt (embedded default), qdrant, pgvector, chroma,
weaviate.
- Terminal panel: `Ctrl+Shift+M`.
- MCP server: every tier can use `scritty serve` over stdio. A current Team
Pilot, Pro, Pro Plus, or Enterprise licence adds `scritty serve --http` over
Streamable HTTP; public HTTP binds require Enterprise. The server exposes 40
tools plus `memory://` resources.
- CLI: `scritty memory ...`.
- Browser/PWA: the same live PTY and memory panel. The listener accepts only
loopback clients by default; every other source receives a 403 before routing.
Any other device requires explicit allowlist/public-origin setup.
## Platform notes
- Linux can register scritty through the `x-terminal-emulator` contract.
- Windows runs scritty as a normal terminal. Default Terminal Application
registration exists, but its attach bridge is not yet usable.
- macOS releases require Apple Silicon (M1 or later); Intel Macs are not
supported.
## Pricing
### Evaluation
- $0, permanently available.
- No card, account, signup, expiry, or network call.
- 25,000 captured exchange-pairs, lifetime.
- Reaching the cap pauses new capture only. Existing memory remains searchable,
exportable, and curatable forever.
### Personal
- $99.99 one-time.
- Unlimited local capture.
- Perpetual license with no heartbeat, account, expiry, or kill switch.
- First year of updates included.
- Optional updates subscription: $39.99/year. Letting updates lapse stops
access to newer builds and does nothing to the installed copy.
### Teams
- Team Pilot: $0, 25,000 pooled pairs or 35 days, 3+ seats.
- Pro: $249.99/month, unlimited local capture, 100,000 federated pairs/month.
- Pro Plus: $749.99/month, unlimited local capture, 400,000 federated
pairs/month.
- Enterprise: from $2,500/month, unlimited local capture, 1,000,000+
federated-pair base band.
- Team pricing meters shared federation infrastructure, never local capture and
never seats.
- Enterprise can be managed, hybrid, or self-hosted; hybrid/self-hosted options
keep captured data in customer-controlled infrastructure.
## How scritty differs
- Agentic terminals such as Warp capture their own built-in agent; scritty
captures supported third-party CLIs run inside the terminal.
- IDE assistants index code in an editor; scritty indexes conversations at the
terminal boundary.
- Memory SDKs require building an agent integration; scritty observes existing
supported CLIs without plugins or wrappers.
- Per-vendor histories remain siloed; scritty puts supported providers in one
corpus.
- Terminal recorders capture bytes without provider attribution or semantic
search.
## Common questions
- Do I need plugins? No. Supported-provider capture happens in the terminal.
- Does local data leave the machine? No, not by default. Team federation is an
explicit opt-in.
- Can any arbitrary CLI be captured? No. Unknown CLIs run normally, but
automatic capture requires a provider entry.
- Is scritty open source? No. The public GitHub repository contains
documentation and issues; builds are distributed from scritty.dev through
the signature-verified installer at cp.scritty.dev.
- How are binaries licensed? Every distributed binary, including evaluation,
uses scritty's commercial binary-licence branch rather than the AGPL
source-code option. Paid use follows the purchase agreement.
## Key facts
- Name: scritty (lowercase).
- Category: terminal emulator, AI coding-agent memory, cross-agent context.
- One-line description: One terminal for every supported AI agent, with a
persistent searchable cross-agent memory you control.
