X3 Browser sessions per agent, stacked PiP, and a right summary card

Open
#402 0 comments 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
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
electron, typescript

Research direction

Start by reading the experience rework in issue #399 and the work on target branch claude/experience-integration. The issue defines backend session ownership and source tracking, plus stacked live PiP cards and a right summary card, but names no files or tests. Done means three parallel sub-agents each have a visible session and PiP, idle CPU stays at 0 with sessions hidden, and the work passes hands-on re-test and review.

Written by the indexing model from the issue text.

Description

Backend:

  • Multiple browser sessions per chat and per sub-agent (separate views and profiles as today). The browser tool addresses a session.
  • Close sessions when their owner ends.
  • Track visited sources (browser and web-fetch tools).

Frontend:

  • One PiP card per live session, stacked (3 visible plus '+N'). Click focuses that session's tab. Live thumbnails.
  • Replace the empty right-column tiles with a compact summary card: folder and branch, Changes ±, Commit/PR, Sub-agents (avatars, live state, thumbnails), Browser sessions, Sources, Terminals, Plan progress.

Gates: 3 parallel sub-agents each get a visible session and PiP. Idle CPU stays at 0 with sessions hidden.

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.