Commit Graph

5 Commits

Author SHA1 Message Date
alan 5425001d82 Send artifacts, runs and pipelines to a new or existing chat
One picker offers a new chat (the saved Open in chat harness and model)
or any open chat. An existing chat gets the reference appended to its
draft and focused, never sent. Artifacts gain the action in their viewer
and gallery; the run and pipeline item becomes Send to chat.
2026-11-13 18:43:14 +00:00
alan 6cd7774811 Open in chat opens beside the active chat and uses a chosen harness
A chat opened from a run or pipeline now goes in a new pane beside the
active chat instead of replacing it, becomes active and takes the
keyboard once built. Settings > Open in chat chooses its harness and
model (models listed from that harness's most recent chat).
2026-11-13 13:34:26 +00:00
alan e5403ae257 Open a run or pipeline in a new chat
The run and pipeline More menus offer Open in chat: a new chat in the
run's (or the pipeline's latest run's) workspace opens on the Chat tab
with a draft naming the run or pipeline and how to inspect or change it.
2026-11-13 12:38:27 +00:00
alan 9695100faa Build chat panes through one content builder
Phase 2.2 of docs/plans/floating-windows.md: buildChatPaneContent wraps a
conversation in the scopes it needs and keys it by the runtime, so the
tiling and (next) a floating window build the same subtree. The tiling uses
it; behaviour is unchanged.
2026-11-10 21:05:41 +00:00
alan 558eedb410 Extract ChatRuntime from the Chat screen
Phase 2.1 of docs/plans/floating-windows.md. The session list controller,
opened rows, accepted models, transcript positions and caches, composer
focus requests and list folds move from ChatScreen's state to ChatRuntime.
ChatScreen builds its own unless one is passed; behaviour is unchanged.
2026-11-10 21:00:21 +00:00