Docs / Auto-Yes
Auto-Yes
A per-session toggle that answers an agent's permission prompt so a long run keeps going while you are away from the keyboard. This page is what it does. For whether you should turn it on, read when to leave it off.
Where is it?
In the session view next to the terminal, and on mobile in the session bar, where it reads Auto on or Auto off.
While it is active the header says Auto-Yes on, and prompts it confirmed are marked in the stream — so you can scroll back and see exactly what got answered for you.
Which prompts does it answer?
Only the ones it recognises as permission prompts. A free-form question, or a menu it cannot identify as a permission prompt, is left alone and the agent waits for a human. That is deliberate.
It confirms whichever option the agent has left highlighted — normally Yes, because that is where the cursor sits. TermLink does not move the selection onto Yes, and it does not read the command about to run and form an opinion about it.
Does it work the same for every agent?
The behaviour is the same; the keystroke is not. TermLink keeps a key per agent rather than sending one and hoping.
| Prompt shape | What Auto-Yes sends |
|---|---|
Numbered menu — 1. Yes (Claude Code, Codex CLI) | Enter |
Cursor Agent — Run (once) (y), Proceed (y) | y |
Codex CLI specifics are on the Codex page.
Is it on or off when I open a new session?
It starts off, but after that new sessions inherit whatever you set last. This catches people, so it is worth being precise about.
The first time you ever use TermLink, Auto-Yes is off. Turn it on for one session and that becomes the default for sessions you open afterwards in the same browser — the app tells you so at the time, with a small notice reading New sessions default to Auto on.
So the thing to check is not “did I turn it on for this one?” but “what is it currently set to?” Before a migration, a deploy, or anything against production, look at the toggle rather than assuming a fresh session starts clean.
The setting is remembered per browser, so a different device can have a different default.
Can I change it mid-run?
Yes, and that is the point of it being a toggle rather than a launch flag. Turn it off and the very next prompt waits for you again.
Because it lives in the browser, you can flip it from a phone — which is usually where you are when you realise a run is going to sit blocked for an hour.
What it is not
Auto-Yes is a convenience, not a safety feature. It does not evaluate what it is approving. Leave it on for work whose blast radius you already accept, and off for anything you would want to look at before it happens.
The longer version of that argument, including how it differs from an agent's own permission modes, is in how to stop Claude Code asking for permission every time.
Checked against the shipping web client on August 25, 2026.
Next: sessions and limits, the CLI reference, or troubleshooting.