Auto-Yes

Answering approvals for you, so a long run does not sit blocked while you are away from the keyboard. There are two places this happens and they work differently. This page is what each one does. For whether you should turn it on at all, read when to leave it off.

An agent session: three settings

A Claude Code, Codex, Cursor or Copilot session carries its own approval setting, in the session header. You pick how far it goes.

Setting	Answered for you
`Ask for everything`	Nothing. This is the default.
`Allow file edits`	File changes. A command still stops and waits for you.
`Allow commands and edits`	File changes, commands, and the agent's other tool calls.

A question the agent asks you is never answered, and neither is a plan it wants you to approve. Those are not on the list in any of the three settings. If the agent wants to know which of two approaches you would rather have, it waits.

When it does answer, it takes the plain allow and nothing wider. Where the agent offers a “yes, and stop asking for this session” option next to the single yes, TermLink does not pick it.

A terminal session: the Auto-Yes toggle

A plain terminal session has no structured approvals to answer, so this one reads the screen instead. It is the Auto-Yes switch under Config, and on mobile in the session bar.

It confirms a highlighted Yes or Allow and keeps answering for as long as the box is up. It takes the first option, which is the single allow, rather than the blanket for this session line under it. A free-form question, or a menu it cannot identify as a permission prompt, is left alone.

This is the path that covers whatever else you run in a terminal, including an agent CLI you started yourself rather than through TermLink.

Where does the starting value come from?

New agent sessions start at Ask for everything unless the host was told otherwise.

Run the host with termlink start --auto-approve edits or --auto-approve all and new agent sessions on that machine begin there instead. Leaving the flag off is the same as --auto-approve off. The full flag list is in the CLI reference.

So the thing to check before a migration, a deploy, or anything against production is what the session is currently set to, rather than assuming a fresh one starts clean.

Can I change it mid-run?

Yes. Change it and the very next approval follows the new setting.

Because it lives in the browser, you can change it from a phone, which is usually where you are when you realise a run is going to sit blocked for an hour. The session shows what the host last confirmed, so a change you make in one tab shows up in the others.

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 TermLink 0.1.4 and the shipping web client on September 22, 2026.

Next: sessions and limits, the CLI reference, or troubleshooting.