MonoCode is gaining the individual pieces: inbox, browser previews/tabs, sessions, worktrees, terminal output, and PR review. The missing power-user layer is a durable task workspace that connects them.
A workspace should be creatable from a GitHub/GitLab issue or merge request, or from a new task. It should retain:
- source work item and its status/review/CI state;
- one or more agent sessions and subagents;
- repository/worktree and branch;
- relevant browser tabs or local preview;
- a compact task status: ready, running, waiting for input, needs review, blocked, done.
The goal is not a project-management product. It is a fast way to reopen an active engineering task tomorrow without reconstructing its context or hunting through sessions, tabs, and repositories.
Useful actions: open/reopen workspace, start a session in its worktree, open the linked PR/issue, surface a waiting agent or failed CI, and archive when the task is complete.
This would complement existing inbox, browser, subagent, and project-picker work rather than replace it.
MonoCode is gaining the individual pieces: inbox, browser previews/tabs, sessions, worktrees, terminal output, and PR review. The missing power-user layer is a durable task workspace that connects them.
A workspace should be creatable from a GitHub/GitLab issue or merge request, or from a new task. It should retain:
The goal is not a project-management product. It is a fast way to reopen an active engineering task tomorrow without reconstructing its context or hunting through sessions, tabs, and repositories.
Useful actions: open/reopen workspace, start a session in its worktree, open the linked PR/issue, surface a waiting agent or failed CI, and archive when the task is complete.
This would complement existing inbox, browser, subagent, and project-picker work rather than replace it.