chrisbanes / chrisbanes/ensemble
Mission Control Phase 2: workspace diff review
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 0
- Avg merge
- 23h 12m
- Merged PRs (30d)
- 84
Description
Context
Final review and run triage need first-class visibility into the changes produced by agents.
Goal
Add a safe workspace diff API and Mission Control diff review surface.
Scope
- Expose changed-file summaries for issue workspaces/worktrees.
- Support staged, unstaged, untracked, deleted, renamed, and binary/unpreviewable entries where Git can identify them.
- Render text patches in the UI.
- Allow refreshing diff state.
- Keep binary content hidden while preserving file-level visibility.
Acceptance criteria
- Operators can inspect changed files and text diffs from the selected issue panel.
- Missing refs, non-git workspaces, and git errors surface clearly.
- Diff APIs do not expose files outside the workspace.
Notes
This complements the workspace browser and should support finalization/review decisions.
Contributor 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.
Research direction
Start by tracing the existing workspace browser and Mission Control selected issue panel, then identify the workspace diff API entry point. Review how Git workspaces and errors are currently handled before defining the diff review flow. Done means operators can inspect file summaries and text patches, refresh state, see clear errors, and never access files outside the workspace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100