Your Gitsi account, inside Termiyo
Browse your repositories, create a new one and work with pull requests from your own Gitsi account.
Read the preview guide: Your Gitsi account, inside TermiyoNew in 0.4.34Work together — every AI account on one jobWork together
Termiyo is the SSH client that puts the AI tools you already pay for — Claude Code, Codex, Gemini CLI and more — on one job, as one crew. Gitsi keeps your team’s repositories on a server you already pay for, and your keys are encrypted on your device before anything syncs.
01Work together
New in 0.4.34Write the job once and press Use all 4 accounts. One plans, the others write, and Termiyo keeps the job moving when a limit hits.
01One account plans.
Pick a manager, or Termiyo takes the first account in your order. In one turn it writes the plan — up to eight tasks — and at the end it writes the report. With other accounts working, that is all it does; on its own, it does the tasks too.
02Termiyo hands out the work.
Dispatch, tracking and reassignment are Termiyo’s own code, not a model’s: one task per account at a time, up to six at once. Each account is told to write text only — Claude runs with its tools off, Codex in a read-only sandbox, Gemini in plan mode.
03A limit doesn’t stop the job.
When an account hits its limit, its task moves to another account at once and carries on from what the first one wrote. The report comes back as Markdown you can copy.
Works with one account — its tasks run one after another — or with all of them at once. Each task spends the allowance of the account that does it.
The jobPlan the move of the checkout service from Redis 6 to Redis 7: what breaks, the rollout, the rollback, and what to test.
Claude · personal
Codex
Gemini CLI
Claude · personal
Gemini CLI
+ 2 more tasks, both running
02The harness
New in 0.4.34Termiyo drives the AI command-line tools you already pay for, under its own control. The Harness tab asks one thing of several lanes at once — a lane is a model on one of your accounts — and shows which account every answer came from.
Question
A 502 shows up only behind the second load balancer. Where do I look first?
Claude Opus
workCompare the two upstream blocks first.
A keepalive timeout on LB2 that is longer
than the app’s idle timeout gives exactly
this: 502s on reused connections only.
Thinking…Answered by work
Claude Sonnet
workCheck LB2’s health check. If it marks a
backend up before the app is listening,
the first requests after a deploy 502 —
its access log shows upstream: -.
Thinking…Answered by work
Claude Opus
personalLook at TLS between LB2 and the backends.
A missing SNI or an old cipher list fails
the handshake, and nginx reports that as
a 502 rather than as a TLS error.
Thinking…Answered by personal
Lanes run on Claude Code today. Carry on uses each lane’s last conversation on this machine; reading each other is one hop, capped, and only when you ask.
Claude Code, Codex, Gemini CLI, ChatGPT CLI, Ollama and llm — or any Anthropic- or OpenAI-compatible key. For the command-line tools there is no key to paste, and nothing goes through our server. The AI panel reads answers aloud, too, in your operating system’s own voices. new in 0.4.26You can now ask your accounts from inside a terminal. Ask Harness in this terminal — Ctrl+Shift+X, or Cmd+Shift+X with the Mac shortcuts — opens a harness> prompt at the bottom of the terminal you are in, and the answer is printed there. The question and the answer stay on your screen and are not sent to the server; a proposed command goes onto your shell’s line with Tab and runs only when you press Enter. Claude Code accounts answer today. new in 0.4.27And now your accounts can take on a job together without leaving the terminal. Type /team and a job at the harness> prompt: a manager account divides it into tasks, your switched-on accounts work on them at the same time, each line showing what it is doing, and the manager writes one report at the end. Nothing is typed into the server — a command in the report is only placed on your shell’s line and runs only when you press Enter. Claude Code accounts take part today.
Each account runs in its own private folder and environment and never inherits another login. Prompts go in on stdin, so they stay out of ps. new in 0.4.23One tool can now hold several accounts, and you add each one with that tool’s own sign-in: Claude, ChatGPT through Codex (on macOS too) or Google for Gemini CLI. No API key is needed.
In the AI panel the same transcript goes to your next ready account, and a line says so: “work’s limit is reached — continuing on personal.” In the Harness pane a spare account switched in has not seen the conversation, and it says that too.
A chip in the status bar names the account that answered last and turns amber at 80%. Termiyo has no live reading of your quota, so there is no percentage bar here — only the figures each tool last reported, read without spending any allowance, and how old they are.
03.env
Termiyo finds every .env on a host or on your own machine, shows which program reads it, and flags the ones tracked by git or readable by everyone. Change one key and it leaves the comments and the order alone — with a diff on screen before anything is saved.
new in 0.4.34 The version you replaced is kept encrypted in your vault, on this device — up to ten versions for thirty days — instead of a plain-text backup next to the file.
It edits files. It is not a secrets manager, and it injects nothing into your programs.
/srv/checkout/.env
read by node server.js
/srv/worker/.env
read by python worker.py
⚠ tracked by git
/etc/billing/.env
read by billing.service
⚠ readable by everyone
# payments
STRIPE_TIMEOUT_MS=3000
API_KEY=••••••••••••
# cache
- REDIS_URL=redis://10.0.3.12:6379
+ REDIS_URL=redis://10.0.3.14:6379
REDIS_TLS=true
Draft — check it first
staging pe api service restart karke uske last 50 lines of logs dikhao
04Voice
New in 0.4.34Talk instead of typing — in English, or in Hinglish written the way you’d type it (or in Devanagari, if you switch that on). Only after you agree does the audio go through Termiyo’s server to Deepgram, a speech-to-text service, and come back as a draft. You read the draft and fix it. Send it to the AI prompt to run yourself, or — new in 0.4.28 — send it to the terminal, where Termiyo runs the one tidied line for you; a command on the dangerous list is still caught first, and nothing is sent while the vault is locked.
Needs you signed in, and counts against your plan’s hosted-AI allowance. Termiyo’s server keeps no audio, and asks Deepgram to leave each request out of its Model Improvement Program; Deepgram’s documentation says data from such requests is kept only as long as it takes to process them.
05Gitsi
New in 0.4.34Host your private repositories on a server you already pay for. No per-seat git hosting, no root, no extra service — your team clones and pushes over plain SSH.
$ git remote add giti ssh://deploy@build-1/checkout.git
$ git push -u giti HEAD:refs/heads/main
To ssh://deploy@build-1/checkout.git
* [new branch] HEAD -> main
# on build-1, after your push
✓ build ✓ test
01
Your laptop can be off; the host has to be up. Termiyo sets up the repository, a restricted shell and the keys over SSH — no root, no daemon, no web port — and nothing passes through termiyo.com.
02
Read-only or read and write, per person. Your teammate needs nothing but plain git, and their key stops working at the end of the owner’s paid period — enforced by sshd itself.
03
A link that lasts one, three or seven days, with an optional passcode. You approve each person by their confirmed address and key fingerprint, and Take back removes their key first. Both of you on a paid plan; a trial doesn’t count.
04
Opens a pull request on GitHub or a merge request on GitLab with a build-and-test workflow for your kind of project, every action pinned to one exact version, and nothing changes until someone merges. A Gitsi repository can run its workflow on its own host after each of your pushes. Paid.
already in the app Or keep a repository on this computer, for you alone — nothing uploaded and nothing running. Free.
Termiyo’s local/SSH repository mode has no web interface, pull requests or issues: it is where your code lives, not a GitHub replacement, and it proves which key pushed rather than who wrote a commit. Share links are off until termiyo.com’s server turns them on. The deploy half of CI is not built yet.
In preview · not yet released
Browse your repositories, create a new one and work with pull requests from your own Gitsi account.
Read the preview guide: Your Gitsi account, inside TermiyoReview recorded commits, then explicitly run a command against a task or the combined result.
Read the preview guide: See what the crew changed06The SSH client underneath
07Security
Safety is not a paid feature. Only the second-person approval needs a team — because it needs a second person.
Argon2id · m = 64 MiB · t = 3
The whole field is one guess.
Argon2id with 64 MiB per guess, XChaCha20-Poly1305 for every record, and X25519 sealed boxes to share a vault. The server never sees your vault’s contents.
It locks after fifteen idle minutes and when the computer sleeps, and only a key press, a click or a menu choice counts as you being there — background checks can’t hold it open. Locking doesn’t end your sessions.
It picks from thirteen fixed actions with checked arguments, and an unattended agent is refused outright on a production host.
The new detector catches 22 of 22 held-out cases with no false alarm on 25 harmless ones. It warns; it never blocks.
An authenticator app and ten recovery codes, on any plan.
An AI agent’s plan that writes to a production host waits for someone else on your team. The server refuses an approver who is also the requester, and the request lapses after an hour. It doesn’t cover commands you type yourself.
Owner, Admin, Member and Auditor; shared vaults; an audit trail.
Alert · api-2
triggered 12:03 · open 14 min
checkout p95 latency above 800 ms for 10 min
api-2 · /var/log/checkout/app.log
12:04:11 WARN redis timeout after 3000ms
12:04:12 WARN redis timeout after 3000ms
12:04:12 ERROR checkout failed: upstream timeout
08Monitoring
New in 0.4.34Connect Datadog or New Relic with your own keys and see hosts, open alerts, logs, APM and SLOs beside the terminal, and open its dashboards in your browser. Nothing is installed on your hosts.
The only change it makes is a Datadog monitor edit — four fields, never the query — after you confirm, refused if the monitor changed in the meantime, and written to the audit log.
Off until you turn it on: a read-only investigation of a waiting alert that names one saved host, while Termiyo is open and unlocked. Never on a production host, and it spends your AI allowance.
Dashboard cards and a console tab on Ctrl+Shift+G, with thirty days of host history from sysstat over your own sessions.
Signed the Standard Webhooks way, retried at 2, 15 and 60 seconds, and a target on your own network is refused unless you tick it.
09Pricing
The client, the crew and every safety feature are free. You pay for sync, for sharing, and for Termiyo’s own AI beyond the free allowance.
$0/ month
One person, one device
$10/ month
Your devices, in sync
A 14-day trial starts when you register; share links and CI need the paid plan itself.
$20/ month
Five people included
Business and Enterprise, and everything each plan includes, are on the pricing page.
Free for one person · macOS, Windows and Linux · no API key for the AI tools you already use
This reaches the same inbox as an email does. We reply to the address you leave.