Add MulmoTerminal — browser terminal grid for running multiple Claude Code / Codex sessions
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- git, javascript, node.js
- Domain
- content
Research direction
Read the contribution guidelines and compare the suggested entry with the existing list format. Add the MulmoTerminal entry to the appropriate section, then confirm its link and description match the proposal and the list’s conventions.
Written by the indexing model from the issue text.
Description
Hi — suggesting a resource for the list. Contribution Guidelines say "Under Construction", so opening an issue rather than a PR. Happy to send a PR instead if you prefer.
Repo: https://github.com/receptron/mulmoterminal
License: MIT
Suggested entry (matching the existing format):
- [**mulmoterminal**](https://github.com/receptron/mulmoterminal) - Browser terminal that runs multiple Claude Code and Codex sessions in a grid, colour-coded by which agent needs input, with tmux persistence, git worktree isolation and phone push.
Suggested section: 🖥️ Clients & GUIs, or 🤖 Agents & Orchestration if you consider multi-session supervision to belong there.
What it does
Each cell is a real PTY running the claude or codex CLI on your own machine, streamed to xterm.js over a WebSocket. The grid colour-codes every session by state — working, blocked on input, done — so the one that needs you is visible without visiting each pane. Sessions survive a reload through tmux, parallel work isolates in git worktrees with one-click PRs, and a finished or blocked turn can send a Web Push to your phone.
Nothing runs in the cloud: your code, your keys, your existing CLI. One command, no install:
npx mulmoterminal@latest
- Dominant language
- No language data
- Stars
- 530
- Forks
- 651
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 jqueryscript/awesome-claude-code
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
All issues in jqueryscript/awesome-claude-code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
cline/mcp-marketplace#3335 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
distrochooser/distrochooser#520 ·
Maintainers usually reply within 2 days
-
[Resource]: WeirOpenresource-submission validation-passed
Difficulty 1/5 Under an hour Newbie friendliness 74/100
hesreallyhim/awesome-claude-code#3295 · 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 74/100
lingdojo/kana-dojo#33228 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Correct class syntax and output examples in the Python OOP and encapsulation lecturesPossibly taken @Sidsmartz claimed this today. Openhelp wanted lesson python v9 cert scope: curriculum
Difficulty 1/5 1-3 hours Newbie friendliness 89/100
freeCodeCamp/freeCodeCamp#71411 ·
Maintainers usually reply within 1 day