Follow-up work from the GUI interaction and mobile pass: map and order
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 1/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
This issue maps follow-up work across the GUI, mobile experience, preview layer, spaces and pairing, settings, and TUI; it does not identify implementation files for the overall map. Start by checking the linked issues and their dependencies, then follow the listed order and shared GUI screenshot requirement. Done means the linked work is closed and its checklist is updated.
Written by the indexing model from the issue text.
Description
This issue is the map of the follow-up work from the November 2026 GUI interaction and mobile pass. Each linked issue is self-contained: it carries its design, the files it touches and its acceptance list. Tick an item here when its issue closes.
Two rules apply to all of it. GUI work is accepted only after real screenshots at desktop width and at phone width (a touch context; a narrow viewport alone does not show the phone layout). Paths and line numbers in the issues were checked against the branch perf/gui-interaction-mobile-pass.
Agent tools: follow-ups to the tool rework
- #3
- #4
- #5
- #6
Timeline: finish the single-window model and adopt it in the GUI
- #7
- #8 — after #7
- #9
- #10 — after #9
- #11 — after #7
Phone: remaining simplification work
- #12
- #34 — after #30, #33
- #13
Spaces and pairing: position bar, switch panel, settings merge, pairing sheet
- #14
- #15
- #17 — after #14, #15, #16
- #16
- #18 — after #15, #16
- #19
- #20 — after #16
- #21 — after #17, #16, #19, #20
- #22 — after #16, #20, #21
Settings and UI rules: remaining pages, session menu sheet, approvals, cleanup
- #39 — after #38
- #23
- #24
- #25
- #26
- #40 — after #39, #23, #24, #25, #26
- #41 — after #39, #23, #24
Preview layer: one resource model whose actions follow the file
- #27
- #28
- #29 — after #27, #28
- #30 — after #29
- #31 — after #27, #30
- #32 — after #27, #30, #31
- #33 — after #27, #29, #32
- #35 — after #27, #33
- #36 — after #27, #30, #33, #35
- #37 — after #27, #32
One select base and one model picker across the GUI
- #38
- #42 — after #16, #39, #23, #24, #38
Session access tokens and terminal status reporting
- #43
- #44 — after #43
- #45
- #46
- #47 — after #44, #46
Promotion: launch drafts, feature pages, screenshots
- #48
- #49
- #50 — after #15, #17, #16, #21, #39, #24, #25, #26, #33, #36, #49
TUI: decided fixes not yet built
- #51
- #52
- #53
- #54
- #55
- #56 — after #53
Tests: failures on macOS and in the GUI suite
- #57
- #58
Order
- Can start now: #3, #4, #5, #7, #9, #12, #13, #14, #15, #16, #19, #25, #26, #27, #28, #38, #43, #45, #46, #48, #49, #51, #52, #53, #54, #55, #57, #58
- Then: #8, #10, #11, #17, #18, #20, #39, #29, #44, #56
- Then: #21, #23, #30, #47
- Then: #22, #24, #31, #40, #41, #42
- Then: #32
- Then: #33, #37
- Then: #34, #35
- Then: #36
- Last: #50, #6
The longest chains are the preview layer (#27 → #28/#29 → #30 → #31 → #32 → #33 → #35 → #36), spaces and pairing (#14/#15/#16 → #17 → #21 → #22) and session access (#43 → #44 → #47).
apps/kimi-code/src/tui/daemon/daemon-tui.ts is edited by several terminal UI issues; land them in this order: #52, #53, #54, #56, #46, #47.
- Dominant language
- TypeScript
- Stars
- 54
- Forks
- 5
- Avg merge
- 2h 54m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from X-T-E-R/kiki
-
Document PowerShell shell semantics and read-only Bash deduplication in Built-in Tools referenceOpendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 54/100
-
documentation
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
area: cli priority: P3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
appandflow/stim#5640 · 1 comment ·
Maintainers usually reply within 1 day
-
Claude Code: hook systemMessage lines never reach the chatPossibly taken @chphch claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
slopus/happy-agent#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
NangoHQ/nango#8285 · 1 comment ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
lingdojo/kana-dojo#34009 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
paperclipai/paperclip#21197 ·
Maintainers usually reply within 1 day