Take one console tool out of full-auto, on your own say-so

What changed

The console (Telegram/desktop chat and MCP connections) has approval modes for keys allowed to act unasked: manual, semi_auto and full_auto. Until now the mode applied to every tool at once — there was no way to say "everything may run itself, except this one thing".

Two new tools now sit beside the approval-mode pair:

• os_set_manual_only — takes tools out of the automatic modes (or brings them back: add, remove, clear).
• os_get_manual_only — lists the tools currently taken out.

A marked tool asks for its approval card in every mode — full_auto included — and it is never removed from the tool list: it stays available by hand. Call it, get the card, approve it, and it does exactly what it always did.

Making a project, a task or a lead by hand has been — and stays — possible the same way: project_create, task_create and crm_lead_create all wait behind an approval card and write nothing until you say yes. The two task-side create tools now also carry the explicit data-change flag.

How to use it

1. In your MCP chat, with a key allowed to act unasked, ask "which tools are out of the automatic modes?" to call os_get_manual_only.
2. Say "take project_create out of full-auto" — that calls os_set_manual_only with {"action": "add", "tools": ["project_create"]}.
3. From then on every project creation brings an approval card first; answer it with os_action_decide (or the approve button in NabuOS, or /approve_<id> on Telegram).
4. To give it back: {"action": "remove", "tools": ["project_create"]}.

Good to know

• Offered only to keys whose owner ticked "act without asking" — the same keys that may change the approval mode.
• The mark is kept for the key and for your account, and it does not expire — a restriction should not switch itself off.
• A same-call confirm still answers the card in place, as before: that is your client asking you, not the tool running unasked.