chimera sessions

List the conversations ``chimera chat`` and ``chimera tui`` have saved, under ``<home>/sessions``. Resume one with ``chimera chat -s <id>`` or ``chimera tui -s <id>`` — one store, so a thread started on either surface continues on the other. These are the terminal's threads, and the ones ``GET /api/sessions`` serves; coding conversations in the desktop app are a different store (``<home>/code_sessions``) with a different shape, and are not listed here. The subcommands are about the app's coding turns that are running now: ``list`` them, ``attach`` to one (follow it, and type to steer it), read its ``logs``, or ``stop`` it.

Subcommands

chimera sessions attach

Follow a running coding turn from its start, and steer it by typing. What you type reaches the agent between two steps, never in the middle of a tool call, and is listed on the turn's receipt. Approvals the turn raises are answered in the app (or with ``chimera code resume`` under Full control); attaching changes nothing about what the turn may do.

Arguments

TURN_IDstrrequired
The running turn's id, or a prefix only it has.

Options

--say, -mstr
Guidance to send first (repeatable). Then follow the turn.
--steerboolean
Send each line typed while following as guidance. Default: on when this is a terminal.