Conversations
Works locallyWorks in the local build today.
A conversation is a thread of prompts with its own memory. A bare prompt continues the sandbox's current conversation, even if you switch harness; --new starts another. Different conversations in one sandbox run in parallel; prompts in the same conversation run one at a time.
harebox new --name convo
harebox prompt current "echo a" --harness shell
harebox prompt current "echo b" --harness shell
harebox prompt current "echo c" --harness shell --new
harebox conversations current
| Event | Survives? |
|---|---|
| Sleep and wake | Yes: the harness process itself keeps running |
| Stop and resume | Yes: the harness's session is on the disk, and HareBox keeps its ID with the conversation |
| Fork | Yes: the fork gets its own copy of every conversation, with a new ID and forked_from set, and each branch continues separately |
A harness's session belongs to that harness. When a conversation switches from one harness to another, the new harness starts its own session in the same conversation.
Events are durable, so a dropped stream resumes from its cursor without loss.