FAQ
Short answers to the questions everybody asks. If yours isn't here, email teep@teep.app or open an issue on GitHub.
Why is it called teep?
Telepathy. You see what the agent is doing in real time, without having to ask.
Does it work with agents other than Claude Code?
Yes. Teep is agent-agnostic — it watches the filesystem, so anything that writes files works: Aider, Cursor background edits, raw scripts, a human co-editor, whatever.
Do I have to use Ghostty?
No. Ghostty is the best experience because of native Kitty graphics. Kitty, iTerm2, WezTerm, and tmux-with-passthrough all work. Anything else falls back to halfblock images — still usable, just lower fidelity.
Why do I need `tmux set -g allow-passthrough on`?
tmux strips graphics escape codes by default. Passthrough lets them reach your outer terminal so images and mermaid diagrams render sharp instead of as pixelated halfblocks. One-time setup in your tmux.conf.
Is teep an editor?
Not really. `i` and `e` exist for quick fixes, but for real editing use your agent or your editor of choice. The agent is the real IDE — teep watches it.
Is teep open source?
Yes. Source is at github.com/teep-app/teep, dual-licensed MIT or Apache 2.0 at your option. Release binaries ship from the same repo.
Can I customize keybindings or colors?
v0.1.0 has minimal config — just a syntax theme. Broader customization is planned. If you have strong opinions, email teep@teep.app.
Does teep work on Windows?
Not officially supported yet. macOS and Linux are first-class. The code is mostly portable; Windows builds may work but are untested.
Does teep phone home?
No telemetry. No analytics. No update checks. It reads your filesystem and renders pixels, that is all.