Drag to rotate, scroll to zoom, click a button to see it in the HUD
Loading the mouse controls…
This demo follows the published app mapping and only controls this page.
See every button and mode ↗
Example code review0 staged
Quick press to jump, or hold for 300 ms and release to stage the file and jump.
This is my current workflow with Better Git VS Code, using button 5 or 8 on either mouse.
Get Better Git VS Code ↗
▶Watching YouTube while I work
Playing
Press Start dictation to see what happens to the video.
An interactive example with no microphone or audio; my real setup uses VoiceInk++ and a separate YouTube bridge.
Get VoiceInk++ ↗
Drag to rotate, scroll to zoom
● ● ●ai-music-video-studio (Workspace)Example names
review.component.ts (Working Tree)
readonly canStage = computed(() =>
− this.changes().length > 0,
+ this.changes().some(change => !change.staged),
);
⑂ codex/reviewaimvs1-review · :4201
One worktree per agent task
Codex creates aimvs<N>-<task-slug> on codex/<task-slug> and adds it to my open workspace. N reserves that worktree’s dev stack until it is removed.
Stack 0 is my main checkout and is never an agent test target. Several agents work at once, each in its own folder.
Worktree lifecycle ↗
Each worktree runs its own stack
AngularNestJSFirebase Auth, Firestore and StorageNx monorepoDocker
Stack 0 mine
- Angular frontend:4200
- NestJS API:3000
- Firebase emulators
- MinIO
- Download Assets Worker
My main services
Stack N one per agent worktree
- Angular frontend:4200+Nnative watcher
- NestJS API:3000+Nnative watcher
Docker
- Firebase emulators
- MinIO
- Download Assets Worker
Private containers; volumes survive stop and removal
Frontend and API are native watchers; the API swaps in each good build. Only the backend runs in Docker. Each stack gets its own test browser: Safari, Firefox or Opera, then Codex’s in-app browser. Firebase Auth still uses staging Auth.
Stack lifecycle ↗
5Previous change
hold(direction) {
− jumpToChange(direction);
+ stageCurrentFile();
+ jumpToChange(direction);
}
8Next change
Hold 300 ms and release: stage this file, then jump
Review each worktree in place
Better Git: press 5 or 8 to jump to the previous or next change. Hold 300 ms and release to stage the current file and jump.
I stage what I’ve reviewed; agents commit when I ask. Their own test files and project instructions have separate staging rules.
Git state and code review ↗
- Checkthe staged snapshot and conflicts with main
- Stopexport and stop the stack; volumes stay
- Landcommit and merge the approved snapshot into local main
- Removethe VS Code folder and Git worktree
- Releasestack number N
One message lands it
Once everything is staged, I ask for mmcdw. Conflicts pause landing for a rebase and review; it never pushes or deletes branches or volumes.
Land and remove a worktree ↗
