kiro-session — Topic Split

Semantic Grouping

LLM groups turns by meaning, not sequence. If you discussed Docker at turns 0-5 and returned at turns 11-15, they stay together.

🧠 LLM analyzes all turns

→

📋 Topic groups in index

→

📄 Temp file on resume

→

🔗 Derivation auto-tracked

    Non-destructive
    Topic mappings stored in the index only — kiro DB is never modified
Temp files generated on-demand when you choose to resume a topic
You load the topic in kiro-cli via /chat load — it becomes a new independent session

  

Topics in Session Detail

Session with 3 topics

============================================================

Session: API Gateway Migration

ID: 612381ac Turns: 58 Tags: [docker] [nginx]

Topics (3):

1. REST API endpoint refactoring

Refactored /api/v1 endpoints, added pagination support.

2. Auth middleware integration ✔ derived

Integrated JWT auth middleware, configured CORS.

3. Load testing and optimization

Set up k6 load tests, optimized DB queries.

============================================================

[r] Resume full session

[1-3] Resume by topic

[t] Edit tags [v] Save [d] Delete [x] Delete topic

[f] Feedback (re-analyze topics)

Resume by Topic

Pick a topic number → cherry-picked turns → temp file → load in kiro-cli.

Resuming topic #1

>

✔ Generated: REST API endpoint refactoring

Turns: 0, 1, 2, 3, 4, 10, 11 (non-contiguous — grouped by meaning)

Resume in kiro-cli:

cd /home/user/docs && kiro-cli chat

/chat load ~/.kiro/tmp/612381ac-topic-1.json

Inferred trust tools:

--trust-tools=fs_read,fs_write,execute_bash,grep,glob

Derivation Tracking

When you load a topic file in kiro-cli, the new session is automatically linked back to its source.

🔗

Automatic

Source markers in temp files are detected on next index scan. No manual linking needed.

🌳

Multi-Hop Chains

Split a derived session again — the chain traces back to the original root session.

📦

Fully Derived

When all topics have derived sessions, the source is marked for archival in cleanup.

🔓

Independent

Derived sessions are fully independent. Deleting one never affects the other.

Fully derived session

Session: API Gateway Migration 📦 Fully derived (3/3 topics)

Topics:

1. REST API refactoring ✔ derived → a1b2c3d4

2. Auth middleware ✔ derived → e5f6g7h8

3. Load testing ✔ derived → i9j0k1l2

Large Sessions

    Chunk-Analyze-Merge (50+ turns)
    Splits turns into ~50-turn chunks, each analyzed independently
Merge pass: LLM reviews all chunk topics, merges duplicates, deduplicates turn indices
A 500-turn session processes in chunks — no context window limits

  

✂️ Topic Split