X2 Composer and messages: docked approvals/questions/plan, live plan checklist, ghost follow-up, model divider, message actions, link chips, model picker fixes

Open
#401 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
electron, typescript

Research direction

This covers composer behavior, plans and to-dos, model selection, message actions, links, and memory suggestions; the payload names no files or tests. Start by reading the experience rework issue #399 and inspect the target branch claude/experience-integration to locate these areas. Done means implementing the listed changes, then completing a hands-on re-test and review; it ships one release afterward.

Written by the indexing model from the issue text.

Description

Composer and dock:

  • Dock approvals, questions, plan follow-ups and to-dos to the composer instead of the transcript.
  • Show the live plan checklist (plan updates and todo tools) as a sticky, collapsible progress bar.
  • Offer a suggested follow-up as ghost text (accept with Tab).
  • Add a 'Model changed from X to Y' divider.

Model picker:

  • Show every current model on the ChatGPT route (refresh the catalog).
  • Fix labels ('Claude Opus 5 5').
  • Use provider logos instead of letter avatars.
  • Remove the always-on 'N hidden' line.

Messages:

  • Copy, read aloud, fork from here, edit and resend, retry.
  • Timestamps on hover.
  • Links rendered as chips with site icons in user and assistant messages.

Memory:

  • Throttle memory-note suggestions to at most one per chat per day, with no transcript line.

Part of the experience rework (#399). Target branch: claude/experience-integration. Ships in one release after hands-on re-test and review.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
17h 33m
Merged PRs (30d)
163

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from musterhq/muster-code

All issues in musterhq/muster-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.