Skip to content

Decide how a Turn's history grows mid-Turn in the Run Projection and headless --json #263

Description

@Sandstorm831

Question

How does the Run Projection carry a Turn whose history grows while it runs, instead of one replaceable preview, so assistant text settles in place and durable rows arrive mid-Turn? Decide message identity, which rows become durable when, how Steer state, Turn duration and the interrupted mark, Entry Turn authorship, and Agent-call rows reach the Projection, and which of these facts headless gains within its frozen --json shapes.

Also settle per-call live command preview budgets and coalescing, retention of supplied partial output when a Turn is interrupted or lost, reconciliation with final native output, placement of Turn-scoped cumulative diffs, and exposure of reported-only context and usage. Keep terminal facts distinct from replaceable previews and command panels bounded by default.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

wayfinder:context-readyWayfinding ticket has curated starting context and may be claimedwayfinder:grillingHITL grilling decision ticket

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions