RunHuddleSession info
Show Session info with the right pane button or ⌘⇧I. It includes the project folder, editor and Finder actions, project notes, repository state, continuation and session details.
Choose an editor in Settings → General → Project editor. Automatic prefers VS Code when available. Use Choose another app… or Check installed editors for other installations. If an explicitly selected editor is missing, select another; RunHuddle does not silently substitute one.
Repository and diffs
The Repository card reports current local Git state: branch, worktree and changed files. This is shared project state, not work attributed to the selected agent. Refresh the card for a new snapshot.
Click the changed-file count to open a Project changes tab alongside Terminal or Conversation. Filter filenames, resize the file/diff divider, select a file and inspect its diff or open it in your editor. Diffs include line numbers and +/− markers. Switching tabs keeps the terminal running.
Counts include staged, unstaged and untracked changes, excluding ignored files. A rename counts once. Binary or oversized files may need your editor. Ahead/behind counts use local upstream refs; RunHuddle does not fetch the remote. This view does not commit, push or open pull requests.
Ask another agent to review
Choose Start a review with another agent…, or Review… in Project changes. Pick a reviewer, select the files and optionally describe the focus and task context. Preview request shows what will be sent.
The request contains compact instructions and scope, not attached diffs or file contents. The reviewer reads the working tree locally. Selecting all changes requests all current changes; a subset names the selected files. It does not use source conversation history or generate a handoff.
Reviews run in the current repository so uncommitted changes remain visible. The prompt requests findings without edits, but this is not a separate security sandbox: normal agent permissions still apply. Other agents or editors can change files during a review.
Project preferences and shortcuts
Expand Project shortcuts → Project preferences… to set the folder’s preferred agent/editor, app/staging/repository links and handoff note. Optional commands start empty.
Each command shortcut first shows the exact command and folder. Run command starts it in your login shell with noninteractive input. Output is bounded and the command can be stopped. Configured commands stop when the app exits; persistent terminals have separate quit behavior.
Isolated workspaces
For a Git repository with a commit, supported launch reviews offer Create an isolated workspace. Inspect the new branch and sibling folder before starting.
The worktree starts from committed HEAD. Dirty and untracked files are not copied. Shared-folder launches instead let both agents work on the same files. Created worktrees are retained after launch errors to avoid discarding work. Project-change reviews stay in the current working tree rather than using an isolated copy.