_Kerman 3c160e137d fix(apiproxy): stop projecting injected context as user steering ...

next-step items now split by origin: user-origin messages keep the
'steering' placement, while agent.inject context (approval notices, task
completion notices, attached snapshots) carries a new 'context' placement
that no surface renders until it is claimed as a durable user/message
context card. Widen the placement unions on the wire and in the client
runtime, add a projection test case, and document the split in the
apiproxy/ui-conversation READMEs and the web-steer chrome agent note.

2026-08-03 16:15:07 +08:00

16 KiB

Raw Blame History

View Raw