11. Operate through Main

Use an identity-first brief

Main can inspect and coordinate through the tools available in its session. An agent with authorized terminal-interface control can also operate the UI.

But a prose request does not magically expose every internal lifecycle method. The native /tan launch is an interactive Main-composer path; Hub start launches a process, not a tan. Do not substitute an ordinary task subagent and silently call it a tan.

For each control request, specify:

1. Discovery: identify the exact current agent and any job.
2. Intent: inspect, message, continue, cancel the job, or explicitly kill the agent.
3. Scope: which files and processes must remain untouched.
4. Evidence: report the actual receipt and resulting state.
5. Uncertainty: stop short of destructive action when identity is unresolved.

Copyable request: inspect without waking

Main, rediscover the Lantern Library label-audit tan, including parked entries. Read its available transcript and report the latest completed result, current agent lifecycle state, and any current backing job.

Do not send it a message, revive it, cancel it, or edit files. Note any missing history, truncated result, or ambiguous identity.

Remember that Main’s Hub job-result inspection can consume settled automatic delivery, as explained earlier.

Copyable request: continue through a message

Main, find the exact retained Tan ID for the Lantern Library label audit. If it is usable or revivable, send it one new request: continue this tangent only, reread the current catalog, count green-shelf books, and do not edit files or resume Main's old checklist.

Report the recipient and delivery outcome. Retrieve its answer when available. Do not assume the original background job has restarted, and do not invent a replacement ID if revival fails.

This uses peer messaging. For the precise user steering-versus-follow-up distinction, use the focused composer controls instead.

Copyable request: explicit terminal intent

Main, rediscover the exact Lantern Library label-audit tan. I want an explicit agent kill with a durable terminal tombstone, not merely a turn interruption, background-job cancellation, or plain registration removal.

Use only an installed control that actually provides that behavior. If it is not exposed to your tools, identify the exact runtime Agent Hub row for the operator's x action and state the limitation. Do not silently substitute another stopping operation.

Preserve the transcript, do not roll back files, and identify any separate processes that still require inspection.

Before accepting “done”

Ask Main to distinguish:

• The control request was accepted.
• The targeted turn or job settled.
• The agent is idle, parked, absent, or terminal.
• The requested project outcome was actually verified.
• External processes and already-written files were inspected where relevant.

These are separate claims.

Your operating habit

Identify → focus or address → submit once → observe → leave safely → review the result or stop the exact target.