Inside
the crypt
Crypt is an LLM chat that lives in a haunted terminal. It is not a dark theme wrapped around a chatbot: the terminal is the product, the crypt is the navigation, and every token has a visible consequence.
A terminal with a world inside
Most chat interfaces hide their machinery. Crypt does the opposite. Open it in Ghostty and you enter a real terminal UI: a sidebar of coffins for multiple conversations, a spirit hub where agents appear as ghosts, a roaming Kiro mascot who critiques prompts, and a bestiary of pixel creatures rendered through the Kitty graphics protocol.
The horror is functional, not ornamental. The header's fear gauge shows how
much of the model's context window is occupied. The status bar counts tokens for the current
chat and the whole session. /usage keeps an almanac across days. When context gets
full, the interface says so and gives you /compact instead of silently throwing
history away.
The agent is visible
Crypt treats an agent as a participant with boundaries, not an invisible HTTP request.
Chats can spawn sub-agents, pass messages between sessions, and link response streams with a
bounded relay depth. Tool calls go through a permission gate: a tool can be allowed, asked for,
or denied, exactly rather than vaguely. The user can stop an in-flight answer with
Ctrl+C; late replies are ignored rather than appearing after the conversation has
moved on.
The roaming ghost gives that philosophy a face. Kiro comments on prompts, flees when the crypt panics, and can be hit. It is a small joke with a serious purpose: an agent should feel present enough to inspect, interrupt and question.
More than a chat screen
- F5 triggers a scare: lightning, panic and a jump scare.
- F6 opens a shop where consumed tokens become coins and buy atmosphere.
- F9 opens Haunt, a platform game in which Kiro sends tokens as ammunition.
- /web searches through available backends, fetches the best results and returns a sourced synthesis.
- /settings manages providers in an encrypted local vault; keys are masked, never logged and never placed in the chat.
Offline modes remain useful. With no key, the TUI still starts disconnected. Smoke renders, previews and help work without a network, which makes the visual shell testable before a model is connected.
The infrastructure behind the atmosphere
The unusual part of the build was not adding features one by one. It was keeping the terminal, the agent loop and the visual world deterministic enough to test. Async replies are drained through a typed bus. Token accounting is separate from history. The encrypted provider vault uses ChaCha20-Poly1305 with atomic writes. The hub and the game share a canvas and a fixed simulation step, so motion does not depend on a lucky frame rate.
user → provider → typed incoming bus → drain → history + almanac
↘ tool gate → sequential tool execution
↘ critic → Kiro's separate apparition
The project also carries its own compatibility layer for Kiro: steering, specs, hooks, MCP, agents, skills, checkpoints and memory. That is not a claim hidden in a presentation slide; these surfaces are parsed and exercised by tests in the repository.
What Kiro changed
Kiro made the architecture more explicit. Specs forced the chat loop, tool loop and visual systems to state their contracts before implementation. Steering documents made security rules persistent: API keys are never displayed, logged or pushed; provider data stays in an encrypted vault; the user can interrupt work. Custom agents and skills made narrow expertise reusable instead of relying on one enormous prompt.
The most valuable result was not speed. It was the ability to test behaviours that normally live only in a developer's head: a cancelled response must not be resurrected by a late event; an unreadable almanac must not be overwritten; a tool denied by policy must not run; a 240 Hz game simulation must remain stable across frame budgets.
Try the project
The public project space is at tradoooo.github.io/Crypte. The source and terminal instructions are on GitHub. It is MIT licensed, runs locally, and supports headless smoke and preview modes before any API key is configured.