Taicli is the workspace for long-running coding agents that your security team can actually approve. Runs fully on hardware you already own — or on any major AI provider through the same interface. Agents draft overnight, hand work off to each other, and pause at every destructive step for a human to sign.
Run fully on-premises — your code never leaves your network, no SaaS account, no telemetry. Or connect to any major provider through the same interface. When a provider has an outage, raises prices, or deprecates a model mid-project, your team keeps working.
Long-context refactors, design docs, senior-level code review. Default for architecture work.
Step-by-step reasoning, test-case generation, and the broadest tool ecosystem for automation.
Cost-efficient batch work, long-document ingest, and multi-modal inputs for spec & diagram review.
Run everything inside your perimeter. Route regulated traffic to models that physically never leave your network.
Every turn in a Taicli session goes to the model best suited to the work: complex refactors to Opus, boilerplate to Haiku, anything touching sensitive files to your local stack. Rules you can read, budgets you can set, overrides when you need them. Teams typically see 40–60% lower model spend without giving up quality on the turns that matter.
userId → customer_id across repo
mechanical · no reasoning needed
haiku
sensitive · stays on-prem
local
taicli --model opus when you want the heavy one; set policy.default: local when your repo must never leave the building. The router is a default, never a cage.
Engineers live in the CLI. Staff engineers, TPMs, and security reviewers live in the browser. Taicli gives them the same session with the same context — edits in one show up live in the other.
When several developers — and the long-running agents they dispatch — operate on the same repository at once, the usual outcome is conflicting edits and lost work. Taicli serializes the writes, attributes every action to the engineer (or agent) who triggered it, and keeps the full history queryable long after the session ends.
Every Taicli project has its own threaded chat — so the debate about a design, the suggestion that sparked it, and the diff it produced all stay in one place. The AI doesn’t arrive at each thread empty-handed; it already knows the history of the project it’s being asked about.
getIdempotencyKey lowercase the header name?IDEMPOTENCY-KEY, Idempotency-Key, and idempotency-key.Point every laptop, CI job, and background agent at one Taicli server. Centralize model credentials, context caches, and policy — so the person who onboards on Friday has the same environment as the one who joined last year, and every agent inherits the same governance.
Restarts are invisible to your developers. Conversations, pending work, and connected sessions survive any upgrade — no lost context, no interrupted workflow. Your finance team gets predictability; your engineers get warnings before they overspend.
Planned upgrades and unexpected restarts leave no scar. Browsers reconnect, in-flight conversations resume mid-sentence, pending work stays queued. What looks routine is an engineering choice your developers never have to notice.
Connect to the monitoring stack your operations team already uses. See live activity, hardware utilization, and per-user cost in real time.
Per-user and per-session spending budgets with daily aggregates. Finance gets predictability; developers get a warning before they overspend.
Taicli plugs into the identity, audit, and security tooling your organization already uses. Single sign-on through your existing provider. Every developer action attributed and recorded in an append-only audit trail. Tiered permissions — read-only, workspace-write, or full access — with approval gates for anything destructive.
Enterprise AI procurement usually stalls on the same questions. Here is how Taicli answers them before the call.
One predictable platform fee covers the CLI, Web, and server. Model spend is pass-through — you bring your keys, we bring the workspace.
A 30-minute pilot reveals more than a month of evaluation spreadsheets. Bring a real repo; we'll bring the environment.