# Hand off a task

> Review a Siphon brief, copy Markdown, or start an explicit task in a named T3 Code target.

# Hand off a task

On the desktop, open a Siphon thread and choose **Hand off**. The **Review handoff** drawer
opens beside your conversation. Drag its divider, or use the narrower/wider buttons, to resize
it; Siphon remembers the width. In a narrow window the drawer sits below the conversation.
The conversation and drawer scroll separately. **Cancel** or the close button dismisses it
without starting a task, and reopening it keeps your edits.

Choose one **Handoff target**, such as “Home T3”, “Work T3”, or **Copy Markdown**. A T3 target
combines the friendly name and server connection; its T3 Code label and address identify where
work will go. Siphon remembers the last target separately from the project. An unconnected
target shows **Connect T3** before the task fields. **Copy Markdown** needs no connection and
copies your reviewed title and brief without starting work or archiving the conversation.

Once the selected T3 target is ready, review the title and brief, then choose its separate
**Project**. Siphon suggests a clear project-name or workspace-path match from the conversation,
or the only project on that target. Ambiguous matches ask you to choose. Review the destination
and project, then choose **Start in T3 Code**. Switching targets keeps the edited brief and
rechecks projects; it never starts work automatically.

T3 creates a new worktree from that project's current HEAD. A new reviewed handoff starts in
**Plan mode**. A voice request that explicitly asks to start work immediately uses **Work mode**
instead, and the drawer shows that saved mode. Permission prompts stay in T3 in either mode.
Uncommitted changes in the original checkout are not copied.

After T3 confirms the launch, Siphon keeps a receipt with **Open in T3 Code** and archives
the source thread only when it still matches the conversation reviewed with the brief.
Continue the work in T3. Siphon does not monitor, approve, merge or deploy it. New activity
after review, including before you press Start, keeps the thread active. Older clients that
cannot identify the reviewed conversation also leave it active.
The desktop keeps the successful handoff drawer open after archival so you can use
**Open in T3 Code**, then close it when you are done.

## Hand off from iPhone

Open a thread and tap **Hand off** in the toolbar to review the same server-backed handoff on iPhone.
Choose a named target and a separate project, edit the title and brief, then explicitly start
the task. **Copy Markdown** also offers a share sheet. The phone shows connection status and
points to desktop setup when a target needs pairing. Edited drafts survive closing and reopening
the sheet. Refresh updates an untouched brief, including its Plan or Work mode. Intentional
edits stay saved; **Use latest brief** replaces them with the current server draft while
keeping your destination choices. If you launch an older edited brief, the newer conversation
stays active. The phone does not store T3 access credentials.
Deleting the source thread from iPhone also removes its saved local handoff brief and retry
request after the server confirms deletion. It does not stop or delete a task in T3.
If another device later restores that deleted thread, it remains usable in Siphon but cannot
be handed off again. Start a new thread for a new handoff; this prevents reusing the deleted
thread's T3 launch key.

## Start by voice or text

The watch uses the conversation rather than a separate handoff screen. You can either prepare
a plan for review or explicitly ask to launch and start work. These commands also work through
the existing voice/text conversation on desktop and iPhone, without a normal conversational
agent configured.

### Prepare a plan

Say or type **“hand off to T3 Code”** in an existing conversation. Siphon prepares a brief
from the conversation and lists your registered T3 projects. It does not start work yet.

1. Review the brief in the reply. You can also open desktop **Hand off** to edit it.
2. Review the selected project when there is a clear match. To change it, or when no project
   is selected, say or type **“use handoff project 1”**, using the number in the list, or
   **“use handoff project”** followed by the exact project name.
3. Siphon names the project and asks you to confirm a new worktree and plan-mode task.
   Say or type **“confirm T3 handoff”** to start, or **“cancel handoff”** to discard the draft.

“Start a thread in T3 Code” and `/handoff t3` also prepare the draft. Ordinary discussion about
handoffs, “yes”, and “go ahead” never launch a task. If the conversation changes after
preparation, Siphon asks you to prepare and review it again. A previous project choice is kept.

### Launch and start work

Launches, confirmations and choices must be affirmative statements, not questions. Transcript
cleanup can improve the displayed wording, but only what you originally said can authorize work.

When you are ready to start implementing, say **“Launch this in T3 Code on my Mac, and then
get started on the work immediately.”** Send the task first and this standalone command next
for an immediate launch. You can also include the idea as one short sentence before the command,
with a full stop or exclamation mark between them. A combined message prepares a brief and
always asks you to review it and say **“confirm T3 handoff”** before starting work, even after
you choose a target or project. Sentence boundaries alone cannot prove that launch wording is
an instruction rather than task content. Name a configured target when you want a particular instance, for example
**“Launch this in Home T3 and start work now.”** The destination must explicitly mention T3.
If your target is named “Home”, say **“Launch this in T3 on Home and start work now.”**
Launch requests for other destinations, such as the simulator, stay with your normal agent.

An explicit standalone launch-and-start request can start directly when the target and project are clear.
Siphon asks a focused question when either is ambiguous. Answer **“use handoff target 1”**
or **“use handoff project 1”**, using the number in the relevant list. For a standalone command,
resolving that choice completes your original launch-and-start request without another confirmation. A recent target
is not permission to choose a different computer. “My Mac” refers to a configured local target
on the Siphon Mac host, not an arbitrary remote connection. T3 still applies its configured permission prompts. This
request starts implementation rather than silently turning it into a planning-only task.

If the wording is unclear, Siphon asks you to describe the task separately and then say the
standalone launch command. It does not launch from quoted, hypothetical or conversational
mentions. A conversation too long for a complete brief needs review in **Hand off** first.

T3 Code and Copy Markdown are the initial targets. Other conversational agents are not
automatically handoff destinations.

## Connect named T3 instances

This integration targets T3 Code 0.1.7, using its shipped native pairing HTTP flow and MCP API.
The pairing flow is verified against that version, not a separately guaranteed stable public API. Start T3 Code and add
your projects there first. In Siphon's handoff drawer, choose **Add a destination…**, enter a
recognizable name such as “Work Mac” or “Home server”, and enter that instance's T3 server URL.
Choose **Add named target**. This saves a target without granting access. When Siphon detects a local T3 installation, it
offers a setup suggestion only. Installed does not mean connected: confirm the actual server URL
and pair it explicitly. Remote targets can always be added manually.

You can add multiple named connections (up to 100), including T3 instances on other computers.
Use a loopback HTTP URL for T3 on the Siphon host, such as `http://127.0.0.1:<your-T3-port>`,
or an HTTPS URL for a remote computer. Use your actual port, not the angle-bracket placeholder.
Do not include credentials, tokens, query parameters or fragments in the URL. The Siphon host
must be able to reach that address. A localhost URL always refers to the Siphon host, not
another computer. Existing `SIPHON_T3_URL` configuration is imported as a named connection.

1. Select the named **Handoff target** in the drawer.
2. In that T3 instance, get a one-time pairing code from **Settings → Sharing & access**, or
   run `t3 auth pairing create` on its host.
3. Enter the code directly in Siphon. Check the target name and URL and the access description,
   then choose **Connect · Supervised**. No browser approval flow is needed.

Connecting explicitly authorizes Siphon for up to 30 days with Supervised access: it can read
projects and threads, and start, message and stop threads across **all projects on that target**.
Permission prompts stay in T3. Read-only grants cannot launch tasks. Siphon clears the pairing
code after submission or dismissal; it does not save the code. It saves only its own grant
locally, never borrowing another agent's credentials.

Once connected, Siphon loads that instance's projects without replacing your edited title or
brief. Choose the target first, then its project. When more than one instance has a project
with the same name, use the connection name to distinguish them. Voice/text project lists also
identify the connection. **Refresh** checks all targets, including ones that are temporarily
offline. A connected target with no projects needs a project added in T3 before you can launch.

**Manage target** remains available when connected. You can rename a connection, reconnect
with a fresh code, or remove its local configuration and saved grant. The server URL is fixed;
add a new named connection to change servers. Removing requires confirmation and does **not**
revoke Siphon's grant remotely: revoke it in T3 separately. Removing a connection or replacing its
grant prevents retrying pending launches under the old grant, so check T3 for those tasks first.

### Credentials stay on the Siphon host

The one-time pairing code normally expires after five minutes and is never saved by Siphon.
The resulting access grant lasts up to 30 days. Expiry or revocation requires a fresh code.
Tokens stay on the Siphon host, not in the desktop API, phone/watch data, or synchronization.

On macOS, Siphon stores credentials in the non-synchronizing **Keychain**. On Linux it uses
**Secret Service**, which requires an unlocked service and `/usr/bin/secret-tool`. Siphon does
not silently fall back to plaintext when secure storage is unavailable. These storage paths
do not imply Windows support.

For a headless Linux host without Secret Service, you can explicitly set
`SIPHON_T3_CREDENTIAL_STORE=private-file`. This opts into **unencrypted** local credential
files, protected by a private `0700` directory and `0600` files. Protect the host, use full-disk
encryption where appropriate, and secure or exclude credential backups. Do not enable this
mode unless you accept that storage tradeoff.

When migrating an existing private token file to secure storage, Siphon verifies the secure
write before deleting the old file. Removing a named connection clears Siphon's local grant;
remote revocation still happens in T3.

## If a launch is interrupted

A timeout does not mean T3 stopped or rejected the task. Siphon saves the request before
sending it and retries with the same ID. Once submitted, the target, project, brief and mode
are locked so retrying cannot silently change the task or expand its permissions. Use **Retry**
or reopen the panel to recover the result. Do not create a duplicate thread manually while the outcome is uncertain.

If you reauthorize T3 after an uncertain launch, Siphon will not retry under the new grant:
T3's duplicate prevention is scoped to the old grant. Check T3 for the original task first.

Wait for ongoing recording or agent work in the Siphon thread to finish before handing it
off. Existing work is never interrupted by opening or canceling the handoff panel.
