Securely record and replay AI agent runs with a local-first flight recorder
Free, no paid tierVisit WebsiteFreeVisit Website
Tracked since2026
The Bottom Line
- Price
- Free, no paid tier. Compare plans
Key facts
- Local-first AI terminal agent with cryptographic receipts for every action the agent takes
- Streams conversations via OpenRouter with live model swapping and MCP tool-call support
- MIT-licensed, zero telemetry, installable in seconds via npm or npx
Pros
- Tamper-evident SHA-256 receipts give a verifiable audit trail of all agent actions, file edits, and tool calls
- Zero external telemetry: all receipts and logs stay on the local machine
- OpenRouter backend means any supported model (leading models, advanced models, etc.) is available without switching tools
- Multiple install paths (npx, global npm, source clone) lower the barrier to a first run
Cons
- Very early stage with minimal community adoption and limited production hardening
- Browser companion requires a separate localhost WebSocket server, adding setup friction
- Documentation is thin beyond the GitHub README, so advanced configuration relies on reading source code
What is Timmy-TUI?
Timmy-TUI (the GitHub repo openrouter-tui-agent) is described by its authors as TIMMY, the Agent Trust OS: a local-first flight recorder and control plane for AI agent work. Every run gets a signed, hash-chained receipt, and replays are designed so they cannot silently rewrite history. It is open source on GitHub.
Key Features
- Signed, hash-chained receipts per agent run
- Local-first control plane
- Replay that refuses silent rewrites
Pricing Plans
Free TrialPricing checked Sep 28, 2026
| Plan | Price | Details |
|---|---|---|
| Free | $0 USD per month |
+3 moreShow less
|
| Team | $4 USD per user/month |
+9 moreShow less
|
| Enterprise | Starting at $21 USD per user/month |
+7 moreShow less
|
Is Timmy-TUI worth the price?
Good value
Timmy-TUI offers a fair pricing structure, especially with its generous Free tier.
The Team tier at $4 per user/month provides excellent value for small to medium teams needing advanced collaboration features. The Enterprise tier starting at $21 per user/month is competitive for large organizations requiring extensive security and compliance.
Hidden Costs & Gotchas
CI/CD minutes and storage overages
How Timmy-TUI's pricing compares
At $4/user/mo, Timmy-TUI is mid-range of its 5 comparable direct competitors ($0.50 to $500/mo across the set).
Entry paid plan, monthly, per user. Pricing checked Sep 28, 2026.
Reviews
$99Free with your review
Write a reviewReview Timmy-TUI, get a free AI guide
Share your experience and we will send you Improve Your Thinking Patterns Using ChatGPT, free.
Best Timmy-TUI Alternatives
Top alternatives based on features, pricing, and user needs.
LangChainFreemium
Build LLM-powered applications
HashiCorp VaultFreemium
Securely store, manage, and encrypt secrets and credentials
mkcertFree
Create local trusted dev certificates
DevinPaid
AI software engineer by Cognition Labs
InngestFreemium
Event-driven background jobs and workflows
PromptfooFreemium
Build secure AI applications with AI security testing integrated into your development workflow.
Still deciding?
Most buyers shortlist 2 or 3 tools before committing. Pull a side-by-side comparison or browse the full alternatives shortlist below.
Explore More
Timmy-TUI FAQ
How does Timmy-TUI help teams audit AI agent actions?
Timmy-TUI provides a tamper-evident audit trail by generating signed, hash-chained receipts for every agent run. These SHA-256 receipts record all agent actions, file edits, and tool calls, and replays cannot silently rewrite history. This makes it suitable for security-conscious teams that need verifiable logs of AI agent behavior.
How does Timmy-TUI compare to Promptfoo for agent observability?
Unlike Promptfoo, which focuses on evaluating LLM outputs, Timmy-TUI is a local-first flight recorder that captures every agent action with tamper-evident receipts. Timmy-TUI keeps all receipts and logs on the local machine with zero external telemetry, while Promptfoo typically sends data to its cloud. However, Timmy-TUI is at a very early stage with less production hardening than Promptfoo.
What are the main trade-offs of using Timmy-TUI in production?
Timmy-TUI is very early stage with minimal community adoption and limited production hardening, so it may not be reliable for critical workflows. Its browser companion requires a separate localhost WebSocket server, adding setup friction. Additionally, documentation is thin beyond the GitHub README, so advanced configuration often requires reading the source code.
Which teams benefit most from using Timmy-TUI?
Teams that need a verifiable, local-first audit trail for AI agent runs benefit most from Timmy-TUI. This includes security teams, compliance officers, and developers working on agentic systems where tamper-proof logging is essential. It is also well-suited for open-source enthusiasts who want to inspect and replay agent sessions without external telemetry.
How is Timmy-TUI priced?
Timmy-TUI is free to use with no paid plan required. It is open source on GitHub, so anyone can install it via npx, global npm, or source clone without any cost.
Can Timmy-TUI replay agent runs with the same model configuration?
Yes, Timmy-TUI replays are designed to faithfully reproduce the original agent run, and the signed receipts ensure the replay cannot silently rewrite history. Because it uses the OpenRouter backend, any supported model can be used, and the replay will use the same model configuration as the original run.
Does Timmy-TUI integrate with existing developer workflows?
Timmy-TUI offers multiple install paths including npx, global npm, and source clone, making it easy to add to existing projects. However, its browser companion requires a separate localhost WebSocket server, which adds some setup friction. All receipts and logs stay local, so it fits into local-first development practices.
How does Timmy-TUI ensure the integrity of recorded agent actions?
Timmy-TUI uses signed, hash-chained receipts with SHA-256 to create a tamper-evident audit trail. Every agent action, file edit, and tool call is recorded, and replays are designed so they cannot silently rewrite history. This provides a verifiable chain of custody for all agent operations.
Source: github.com