mirror of
https://github.com/Kilo-Org/kilocode.git
synced 2026-09-17 17:43:04 +08:00
Mark IJbema
a4c4cf5f52
Replace the flat issue list in the migration plan with 37 detailed doc files, one per issue, grouped into ui-polish/, features/, migration/, error-handling/, performance/, infrastructure/, and cli-side/ directories. Each doc describes the problem, what remains to be done, and implementation notes — readable without opening the GitHub issue. The migration plan tables now link to these docs instead of bare issue references.
1.4 KiB
1.4 KiB
Switch to Session Turn
Priority: P2 Status: 🔨 Partial (assigned) Issue: #6244
Problem
The CLI introduced a Session Turn concept — a structured unit of work within a session that groups related messages, tool calls, and results. The extension currently works at the raw message/part level, which makes it harder to:
- Track the lifecycle of a single agent turn (start, running, complete, error)
- Group messages for display (e.g., collapsing all tool calls within one turn)
- Implement features like "retry this turn" or "edit and retry"
Remaining Work
- Understand the
Session TurnAPI in the CLI — look atpackages/opencode/src/session/for the turn model - Update the extension's session state management to track turns, not just individual messages
- Adjust the webview's message rendering to group content by turn where appropriate
- The SDK (once #6243 is done) should expose turn-level endpoints natively
Implementation Notes
- This is primarily an architectural refactor of how the extension consumes session data
- The Agent Manager is particularly relevant here: turn-level tracking enables better "what is this agent doing?" visibility
- Coordinate with the Session Turn SDK work — the SDK should expose turn methods cleanly before migrating the extension