# ConnectOnion 1.9.3b2 (beta)

## Install this preview

Stable remains 1.9.2. Install this opt-in beta by exact pin:

```bash
python -m pip install --upgrade 'connectonion==1.9.3b2'
```

## The sender's conversation, as a thread of its own

The person you hand a session to pastes one line into Codex or Claude Code, and
their agent accepts and does the work. Their thread then held only that line,
the agent's tool calls and its summary. Your conversation was in no thread at
all; only `co handoff open`, which the page never mentions, replayed it (#2513).

- **Accept writes it.** Run inside Codex or Claude Code, `co handoff accept`
  adds a second thread, `Handoff from <you>: <title>`. Your messages are labelled
  with your name and the day, your agent's replies as `<you>'s Claude Code` (or
  Codex). It ends in the report, with Discussed, Concluded, Still open and the
  diagram, and "You can keep asking me here."
- **Where to find it.** The agent passes on one line. In Codex: the conversation
  list (`/resume`, or the app's sidebar), or `codex resume <id>`. In Claude
  Code: `claude --resume <id>`, or its list.
- **A sandbox costs the thread, not the handoff.** Codex's workspace-write
  sandbox keeps `~/.codex` read-only. Accept still completes, and the agent says
  to run `co handoff thread <id>` outside it.
- **`co handoff thread <id> [--agent codex|claude]`** adds an accepted
  handoff's conversation to either agent, in the current folder.

Checked on Claude Code 2.1.300: the session is listed in `claude --resume` under
its title, opens with the labels, tables and diagram, and answered "what was
decided, what is open" from the replay alone. Checked on Parrot with Codex
0.162.1: the thread is listed in `codex resume`'s picker and opens the same way.
A paste run in the workspace-write sandbox completed the accept and printed the
`co handoff thread` line.

The prompt now pins 1.9.3b2, so a recipient gets this. Handoffs already sent
keep the version they were sent with.