Visible work
Every task, command, preview, and file edit stays attached to the workspace timeline.
The governed workspace for AI coding agents.
Run agents, approve risky actions, and keep every tool call, task, preview, and memory trail visible in one operator-controlled workspace.
When Trejo wants to edit code, run tests, or publish a deploy, Hub shows the repo, tool call, permission mode, diff, and approval point before anything risky happens.
Every task, command, preview, and file edit stays attached to the workspace timeline.
Permission modes make risky actions explicit instead of burying them in a chat transcript.
Memory, logs, and audit trails make agent work inspectable after the tab, model, or session changes.
Tunc Hub lets agents keep working while operators keep the decisions, approvals, and audit trail.
Parallel tasks, checks, and previews continue while your team reviews the moments that matter.
Tool access, permission modes, and deploy gates are visible before an agent can change something important.
Keys, memory, policies, and audit trails stay under your rules instead of disappearing into a prompt window.
Chat, agents, tools, previews, memory, and permissions are grouped around one job: keep AI work visible, reviewable, and recoverable.
Pick the model: Claude, OpenAI, DeepSeek, your call. Ask questions, get answers grounded in the real repo, not a guess from training data.
AI reads files, runs commands, uses git, opens PRs, and checks its work in a browser. All inside isolated workspaces (local or cloud), so your laptop stays untouched.
Spawn agents to plan, refactor, review, or implement while you keep moving. Nudge them, stop them, or take over whenever you want.
Preview the app, the diff, the docs, or the browser session right next to the chat. No app-switching, no guesswork about what changed.
Every chat, plan, task, and tool call is saved against the workspace. Restart the app, switch devices, come back next week. The context is still there.
Decide which models, tools, and credentials each workspace can use. Set policy once. Apply it everywhere your team works.
Give each AI a name, a role, and a co-author signature, so reviewers, PRs, and commits always show exactly who (or what) did the work.
Allow some tools, deny others, ask before risky ones. AI doesn't even see the tools you've hidden. No blank checks.
Every tool call, every approval, every diff is logged against the workspace. Useful for debugging, cost, security, or just answering "wait, why?"
It's a desktop app. You open it, sign in, and you're working. The technical bits happen quietly in the background.
AI doesn't replace your team.The Tunc.AI principle
It just stops slowing them down.
Everything AI does is visible, approvable, and reversible. Not buried in a settings tab. Right on the chat surface, where the work happens.
Give each AI a name and a role. Backend engineer, frontend specialist, code reviewer, QA. The persona shapes how it speaks, what it can do, and whose name shows up on the commit.
Lock a persona to a workspace or company. The right AI runs the right work. No mystery.
AI doesn't need every tool every time. Pick what each workspace can use: shell, git, file writes, browser, MCP servers, your own integrations.
Lock down anything risky. Hide what you don't trust. AI doesn't even know the hidden tools exist.
Four modes. They're visible on the chat surface, so you never wonder what AI is allowed to do right now.
In Auto, the safer stuff runs, the dangerous stuff is blocked, the iffy stuff still asks. Bypass exists, but only when you explicitly choose it.
Every chat, plan, tool call, and approval is logged against the workspace. When you need to know what happened, what AI tried, what got approved, what didn't, it's all there.
Useful for debugging, sharing decisions with the team, or just answering "why did it do that."
Your code, your keys, and your team's identity stay where they belong. Hub is just the app you use. Core is the backend that ties workspaces, credentials, and policies together. Both honor your existing security model.
Want everything private? We white-label Tunc Hub and Tunc Core, then deploy a private Core in your cloud or on your servers. Your domain, your sign-in, your policies. Your data never leaves your perimeter.
Same desktop experience your team already trusts, with your logo on it.
Tunc Hub ships as a macOS desktop app. Public installers are distributed as signed DMG files; in-app updates use signed Tauri updater artifacts served through Tunc Core release metadata.