chimera chat

Interactive multi-turn chat — your terminal right-hand. Requires a key. The whole conversation is saved after every turn, under ``<home>/sessions``, and picked up again on the next run. ``chimera sessions`` lists the threads and ``chimera chat -s <id>`` resumes one; ``GET /api/sessions`` serves the same files to any HTTP client. Coding conversations in the desktop app are a different store — ``<home>/code_sessions``, which keeps the model's own message list and its turn receipts rather than prose pairs — so a thread does not travel between the two. A resumed turn is labelled as restored in the next prompt, and one that ran while untrusted content was in the conversation comes back inside the data fence; a turn saved before that was recorded is treated the same way, because nothing measured it — and a dim line under each reply now says so on screen. Memory recall is scoped to ``--workspace``: that folder's facts, plus the ones stored with no project at all. ``--max-usd`` bounds the whole thread rather than one turn, and ``/solve`` hands the conversation's task to the same verified loop ``chimera solve`` runs, inside that same ceiling.

Параметры

--model, -mstr
Override the model slug.
--max-stepsintпо умолчанию: 6
Max tool-calling steps per message.
--workspace, -wstrпо умолчанию: '.'
Workspace root for tools.
--fuseboolean
Route deep-reasoning turns through fusion.
--cascadeboolean
Tiered routing: weak -> gate -> mid -> gate -> fusion (cheap by default).
--no-memoryboolean
Don't recall long-term memory.
--session, -sstr
Resume a specific session id (see 'chimera sessions').
--newboolean
Start a fresh session instead of resuming.
--max-usdfloat
Stop once this conversation has spent this much (the whole thread, not one turn).
--write-regionstr
Comma-separated globs the file-writers may touch (e.g. 'src/**,*.py'). A write outside is refused — blocks an injected instruction from rewriting an unrelated file.