TIMMYTUI is a local-first terminal agent trust console for builders. It combines OpenRouter model selection, MCP → CLI evidence bundles, a safe local filesystem/workspace, cmux launch, Browser Companion mirroring, local logs, and sealed TIMMY receipts with manifest hashes. Cloudflare-backed receipts, memory, and deployment workflows are next.
Hey PH — TIMMYTUI is my attempt at making local AI agent workflows more inspectable.
Most agent tools focus on getting the model to act. TIMMY focuses on what happens around the action: model choice, tool evidence, filesystem context, workspace launch, logs, and receipts.
Current V2.1 flow:
1. Pick an OpenRouter model
2. Paste an MCP server URL
3. Generate a local MCP → CLI evidence bundle
4. Open the workspace in cmux
5. Mirror the session in Browser Companion
6. Run /agent-proof
7. Review a sealed TIMMY receipt with a manifest hash
The repo is open source and production-demo ready for controlled local use. It is intentionally local-first: no hosted SaaS account is required to try the core workflow.
Roadmap:
• Cloudflare-backed receipt portal
• D1/R2 receipt archive
• Durable Object workspace memory
• Vectorize semantic recall
• TIMMY Pane Pro for multi-agent state visibility
• custom MCP → CLI Receipted Packs
I’d love feedback on the receipt schema, MCP → CLI bundle format, and which Cloudflare/MCP workflows should come next.
Report
@will_meldman Congrats on launching! With the safe local workspace, does TIMMY-TUI sandbox filesystem access via traditional containers, or is it handled via software-level permission layers
TIMMY-TUI currently handles this through software-level permission layers, not a traditional container sandbox by default.
The “safe local workspace” means runs are scoped to a declared workspace root, tool access is made visible before execution, and changes are recorded into local receipts so you can inspect what happened afterward.
Containers are a great next layer for stricter isolation, especially for untrusted repos or shared team workflows. The current focus is local-first visibility, permission clarity, and auditable agent work without forcing every user into Docker from day one.
Report
No reviews yetBe the first to leave a review for Timmy-TUI
Timmy-TUI
@will_meldman Congrats on launching! With the safe local workspace, does TIMMY-TUI sandbox filesystem access via traditional containers, or is it handled via software-level permission layers
Timmy-TUI
@nicole_das_neves_matebese Thanks Nicole!
TIMMY-TUI currently handles this through software-level permission layers, not a traditional container sandbox by default.
The “safe local workspace” means runs are scoped to a declared workspace root, tool access is made visible before execution, and changes are recorded into local receipts so you can inspect what happened afterward.
Containers are a great next layer for stricter isolation, especially for untrusted repos or shared team workflows. The current focus is local-first visibility, permission clarity, and auditable agent work without forcing every user into Docker from day one.