Source Control in Influxx: Diffs, Pull Requests, and Checks
Source Control in Influxx is the shipping surface for agent work. After an agent writes code in a worktree, you review diffs, leave line notes, stage and commit, push, open a pull request or merge request, and watch CI status—without bouncing between a separate IDE, a browser tab for GitHub or GitLab, and a chat window. This guide covers the Source Control panel, annotated diffs (review notes), pull request creation, Checks and PR Checks, workspace comments, and the full review-to-merge loop so you can ship from the cockpit with confidence.
What this guide covers
You will learn how to open Source Control with the keyboard shortcut, stage and unstage files, write or generate commit messages, annotate AI diffs and send notes back to a running agent, create hosted pull requests or merge requests, monitor checks without context-switching, and clean up worktrees after merge. Everything here reflects shipped product behavior: git operations scoped to your worktree, review notes stored as worktree metadata, and hosted review flows that are first-class for GitHub and GitLab while remaining provider-aware for Bitbucket, Azure DevOps, and Gitea.
Influxx is built around isolated git worktrees. Each feature workspace is a real checkout with its own dirty tree, terminals, and metadata. Source Control is the right-sidebar panel that operates on that checkout. Agents do the implementation work; Source Control is how you inspect, correct, and publish it. The panel sits next to Explorer, Agents, Checks, Ports, and Attached worktrees on the right activity bar—one multi-tab cockpit rather than a separate “git app.”
Open Source Control
Select the active worktree in the left sidebar, then open the Source Control panel from the right activity bar, or press ⌘⇧G on macOS (Ctrl+Shift+G on Windows and Linux). The panel lists unstaged, staged, and untracked changes for that worktree’s path, with branch context (ahead/behind relative to upstream when available), commit area controls, and entry points for Create PR / MR when your host supports it. Toggle the right sidebar with ⌘L / Ctrl+L if the activity bar is collapsed.
- Right activity bar: Explorer, Agents (AI Vault), Source Control, Checks, Ports (SSH), Attached worktrees—Source Control is the git shipping surface for the selected worktree.
- Keyboard: ⌘⇧G / Ctrl+Shift+G focuses Source Control; shortcuts use Mod = ⌘ on macOS and Ctrl elsewhere, remappable in Settings → Shortcuts.
- Worktree scope: Status, staging, commit, and push always apply to the active worktree checkout, not a shared global dirty tree across agents.
- Providers: Source Control is provider-aware for GitHub, GitLab, Bitbucket, Azure DevOps, and Gitea so branch and hosted-review chrome match the remote you use.
Review, edit, and commit without leaving Influxx. Diffs, line notes to the agent, commits, PRs, and checks are the same cockpit—not a detour through three other apps.
Stage, unstage, commit, and push
Source Control shows changed files in staging areas: unstaged, staged, and untracked (plus committed history surfaces where available). You can stage individual files or use bulk Stage All when eligible, unstage the same way, open any changed file in the editor, and write a commit message in the commit area. Optional AI commit message generation fills a draft from the staged patch so you edit once and commit. Push publishes the branch to the configured remote; branch context stats show how far ahead or behind you are of origin (or the tracked upstream).
Typical commit flow from Source Control
Open Source Control for the worktree. Review the file list and open diffs for files that matter. Stage the paths you want in this commit (or Stage All when the tree is clean of submodule-only caveats). Enter a commit message, or generate one with Source Control AI when enabled. Commit. When you are ready to share the branch, push. If push or commit fails, Influxx can surface failure summaries and offer agent recovery actions (commit failure fixes, push failure fixes) so you launch a focused fix pass instead of decoding remote errors alone.
- Stage / unstage: Per-file actions and bulk Stage All / unstage controls keep the commit set intentional.
- Open in editor: Jump from a changed path straight into the file or combined diff for review.
- AI commit message: Optional generation uses staged files and patch context; you always review the text before committing.
- Push: Publishes commits to the remote; fork and upstream edge cases surface in push-target labeling when applicable.
- Discard: Discard changes flows confirm before wiping uncommitted work—use deliberately on agent experiments you do not want.
Git and Source Control settings live under Settings → Workflows → Git & Source Control (open Settings with ⌘, / Ctrl+,). Source Control AI settings control whether generation is enabled, which agent writes commit messages, pull request details, and branch names, per-operation instructions, and PR creation defaults such as draft mode, using a host template, generating details when the composer opens, and opening the review after create. Repo-level overrides can refine those defaults per project without changing your global recipe.
Annotate AI diffs (review notes)
Review notes—also labeled AI notes—are line or selection comments on diffs. They are the core “send feedback to the agent” loop: you mark what is wrong or preferred on the modified side of a diff, then send those notes into a running agent terminal (or a launch path) so the agent can patch the same worktree without re-explaining the whole PR in prose. Notes appear on the diff itself, in the Source Control right sidebar Notes section (with a count), and as an AI notes chip on single-file headers.
How to leave and send review notes
Open a file diff or the combined diff for the worktree. Add a note on a modified-side line from the gutter or popover. Collect notes across files as needed. Use Send notes and choose All unsent notes or This file to deliver into a sendable agent session. After send, notes record sentAt; editing a note clears sent state so it becomes unsent again and can be redelivered. From the notes actions menu you can also Copy all notes or Clear all notes… when you want a clipboard handoff or a clean slate.
The prompt format delivered to the agent is structured for precision: file path, line number, and your comment (for example, File: path/to/file.ts, Line: 42, User comment: Prefer early return here). That keeps agent context tight compared with pasting an entire review essay. Send requires a sendable agent terminal—statuses such as not-ready, permission, or no-active-terminal block send until an agent session is ready to accept input.
- Storage: Review notes live in worktree metadata. They are not Git commits and are not automatically GitHub PR review comments unless you also use hosted review on the provider separately.
- Visibility: Diff gutter, Source Control Notes section with count, and AI notes chip on single-file headers stay in sync for the worktree.
- Send scope: All unsent notes vs This file lets you batch a full review or iterate one path at a time.
- Unsent after edit: Editing a sent note clears sentAt so follow-up guidance is not treated as already delivered.
Review notes are how you steer the agent on the diff itself—line-accurate feedback, not another vague chat turn about “the auth module.”
Markdown review notes
The same review-note pipeline works on markdown content in Rich mode. Enable Markdown Review Notes under Settings → Editor (on by default). Open a .md file in the Rich Editor, select text, and add review note cards. Copy notes for an agent or send unsent notes through the same send menu used on code diffs. Use this when the agent’s primary artifact is a plan, design doc, or README rather than a TypeScript module—feedback still lands as structured notes instead of a free-floating message.
Workspace comments vs review notes vs sidebar notes
Influxx has several “notes” surfaces that look similar in marketing copy but store data differently. Review notes are line comments on diffs for agent feedback. Workspace comments are a short sticky field on the worktree card—not a document in .influxx/notes. Sidebar notes are markdown plans under .influxx/notes in the worktree, openable as editor tabs and runnable as agent prompts. Use the right surface for the job so search, badges, and send behavior match what you expect.
How to set a workspace comment
Open Edit Worktree Details from the worktree card menu or pencil control. Fill Comment (placeholder: Notes about this worktree…). Markdown-lite is supported. Save. A Workspace notes badge appears on the card when the field is non-empty. Hover the card for the rendered comment and Edit notes. The comment is searchable in the worktree palette and can also be set from the CLI with worktree set --comment. It is intentionally short—sticky intent for humans browsing the board, not a substitute for sidebar plans or review notes.
- Sidebar notes: Plans bound to a workspace; Run builds a context pack and launches an agent.
- Review notes: Diffs + Source Control; worktree metadata; line comments to send to an agent.
- Workspace comment: Worktree card meta; one sticky field; board and palette discoverability.
- Markdown tabs: Any .md path for long-form docs; optional markdown review notes in Rich mode.
Create a pull request or merge request
After commit and push, use the Create PR / MR composers for hosted review. GitHub and GitLab paths are first-class. The Source Control header keeps Create PR visible as a stable toolbar anchor—even when the composer body is open or the action is temporarily disabled—so shipping never becomes a scavenger hunt. Link worktrees to issues and PRs via Edit Worktree Details (GH issue / GH PR fields and related host links) so the workspace stays tied to the review it will produce.
Ship a hosted review from Influxx
Ensure the branch has the commits you want and is pushed (or complete the publish step the Create PR intent requires when remote history is missing). Open Create PR / Create MR from Source Control. Fill title and body, or generate pull request details with Source Control AI from branch comparison context (base branch, commit summary, changed files, patch). Apply PR creation defaults from settings: draft, host template, generate details on open, open after create. Submit. Optionally open the PR page in the embedded browser if you want the host UI without leaving the cockpit. On mobile native chat chrome, Create PR opens the Source Control / PR hub with the same intent so you are not left with a dead navigation-only control.
- AI PR details: Generation can fill title and body from branch, base branch, current fields, commit summary, changed files, and patch—always editable before create.
- AI branch naming: Source Control AI also supports branch name generation as a separate text action when you want consistent naming from prompt context.
- Draft defaults: prCreationDefaults can prefer draft reviews, template usage, auto-generate on open, and auto-open after create—globally or per repo.
- Fork-aware compare links: Manual review URLs qualify fork heads when the push target differs from the base repo so compare links stay correct.
- Host actions: Hosted review chrome surfaces provider-specific state and actions once a PR/MR is linked or discovered for the branch.
Hosted review is not a replacement for your git host’s full review UI—it is the in-cockpit path to create the review, keep the worktree linked, and stay on top of status. There is no special “merge worktree” product verb beyond git: you merge on GitHub, GitLab, or your host of record, then delete the workspace in Influxx when you are done.
Checks and PR Checks
Checks and PR Checks panels surface CI status so you can wait on green without context-switching to the browser—unless you choose the embedded browser for the PR page itself. Open Checks from the right activity bar. When a pull request is linked or discoverable for the branch, PR Checks fold host check runs into the same operational loop: poll for updates, expand job details, and react when something fails. Folder-workspace PR Checks rows can aggregate status across attached worktrees when you are coordinating multiple checkouts under one project folder.
Working with failing checks
Watch Checks / PR Checks after push or PR create. Expand failing jobs for detail when available. Use Source Control AI launch actions for broken checks fixes when you want an agent to own the recovery prompt from the failure summary. Related launch actions cover conflict resolution and review comment resolution so the same agent-delivery machinery that handles commit and push failures can also address CI and review friction. Refresh breadcrumbs and polling keep status current while you stay in the worktree.
- Checks panel: CI status for the active context without leaving Influxx.
- PR Checks: Hosted review-aware check status for the linked or discovered PR/MR.
- fix checks (AI): Launch an agent with a failure-oriented prompt so recovery stays worktree-scoped.
- Embedded browser: Optional PR page view when you need the host UI, still inside the cockpit tab strip.
Green checks should not require a second monitor full of browser tabs. Wait, diagnose, and re-run the agent loop from the same worktree that produced the change.
End-to-end: agent work to merged PR
The product merge-and-cleanup path is deliberate and short. An agent works in a feature worktree. You review diffs, annotate with review notes, send notes until the change is right, then commit and push from Source Control. Create a PR/MR and watch Checks / PR Checks. Merge on the git host. Delete the workspace in the UI (preflight for dirty state and lineage) or remove it with the CLI worktree rm command. Isolation is the worktree: parallel agents each get their own checkout so you can compare diffs, keep the winner, and delete the rest without shared dirty-tree collisions.
Recommended shipping checklist
Confirm the worktree board status makes sense (In review when you are on diffs and PR; Done after merge if you track that way). Open Source Control and walk every meaningful diff. Leave review notes on anything the agent should fix; send unsent notes and re-review. Stage only what belongs in this commit; generate or write a clear commit message. Push. Create PR/MR with accurate title and body (AI draft is fine—edit for humans). Link the worktree to the issue/PR fields if not already linked. Watch Checks until green or until you launch a fix agent. Merge on the host. Delete Workspace after preflight. Capture a sticky workspace comment early if teammates need one-line intent on the card.
- Board statuses: Todo · In progress · In review · Done—use In review while diffs and PR checks are live.
- Parallel experiments: New Workspace (⌘N / Ctrl+N) with the same prompt across worktrees; compare Source Control diffs; keep one winner.
- Preflight delete: Workspace deletion checks dirty state and lineage so you do not silently drop unfinished or stacked work.
- CLI parity: worktree create/set/rm and related commands mirror the UI for automation and agent-driven shipping.
Source Control AI actions at a glance
Source Control AI is not only commit messages. Text actions include Commit message, Pull request details, and Branch name. Launch actions include Commit failure fixes, Push failure fixes, Broken checks fixes, Conflict resolution, and Review comment resolution. Each action can use a configured agent (or custom command), optional args, and a command template with variables such as basePrompt, branch, stagedFiles, stagedPatch, baseBranch, commitSummary, changedFiles, and patch. Configure defaults under Git & Source Control; override per repo when a monorepo or package needs different agents or instructions.
Generation always gathers context Influxx already knows how to collect safely for that operation—staged diffs for commits, branch comparison for PR details, failure summaries for fix launches. You remain the author of the final commit message, PR body, and decision to push or merge. AI accelerates the paperwork of shipping; review notes and Checks keep the quality loop closed with the agent that wrote the code.
Provider awareness and integrations
Connect GitHub and other task sources during setup (Settings → Onboarding checklist tracks Connect integrations). Source Control remains useful on local git alone, but hosted review creation and Checks shine once the remote host is connected. Provider-aware labeling covers GitHub, GitLab, Bitbucket, Azure DevOps, and Gitea. First-class Create PR / MR composers prioritize GitHub and GitLab. Task Sources can start workspaces from GitHub, Linear, or Jira items so the PR you create closes a loop that began as a tracked issue.
- GitHub: PRs, issue/PR fields on worktree details, Actions-style checks surfaces, compare links including fork heads.
- GitLab: MR creation path and merge-state awareness in hosted review chrome.
- Other hosts: Provider-aware git operations for Bitbucket, Azure DevOps, and Gitea even where composer depth differs.
- Integrations checklist: Setup guide steps include connecting integrations and multi-repo work so Source Control is not empty of remotes.
Diffs in the wider cockpit
Source Control is the hub, but diffs also open as center-tab surfaces: single-file diffs, combined diffs, and PR review unified diffs used by hosted review. From a quick start path—plan in a sidebar note, Run the note as an agent, then review and ship—you land in Source Control with ⌘⇧G, add line notes, commit, push, and create a PR from the same panel. Explorer remains available for filesystem navigation; Agents (AI Vault) for session history; Checks for CI; Ports for SSH port forwarding when remote work is in play. The layout law is one left sidebar, one middle tab strip, one right activity bar.
Quick path: plan → agent → Source Control → PR
Write or open a sidebar note with the plan. Hover the note and click Run to launch an agent with a context pack. When the agent finishes (or while it works), open Source Control. Annotate diffs and Send notes for any fixes. Stage, commit (optional AI message), push. Create PR/MR. Watch Checks. Merge on the host and delete the workspace. For competing implementations, spawn multiple workspaces with the same prompt first, then apply this path only to the winning tree.
Mobile and remote sessions follow the same shipping verbs. When native chat exposes Create PR, it opens the Source Control and PR hub and can auto-run Create PR intent once eligibility is ready—push-create rather than a decorative button. Remote hosts and Remote Influxx Servers (Beta) keep git and agent work on the machine that owns the checkout while the cockpit UI stays familiar. Always verify which worktree is active before bulk stage, discard, or push.
Practical tips for cleaner agent PRs
Prefer small staged commits over one giant blob when the agent touched many concerns—review notes and check failures are easier to attribute. Keep workspace comments short and human; put plans in sidebar notes. Treat review notes as the contract for agent follow-ups: specific lines beat “make it better.” Use draft PRs when AI-generated details need a human pass before reviewers see them. Leave Checks open while the agent fixes CI so you see green without refreshing a browser. After merge, delete the worktree promptly so the board and disk stay honest.
- One concern per commit: Staging discipline makes AI commit messages more accurate and reviews faster.
- Send notes early: Correct the agent on the first wrong approach before it multiplies across files.
- Draft then open: PR defaults can create drafts so title and body can be polished in-cockpit first.
- Do not confuse note types: Review notes are not PR review comments on the host; workspace comments are not sidebar plans.
- Preflight before delete: Dirty or stacked lineage worktrees need a conscious cleanup, not a casual discard.
Source Control is the agentic shipping desk: the agent writes in isolation; you annotate, commit, open the PR, and wait on checks in one place—then merge on the host and retire the worktree.
Related Influxx topics to explore by name in Help and product Notes: Worktrees overview and isolation model; Parallel agents; Agents overview and launching agents; Sidebar notes and running notes as agents; Cockpit layout and keybindings; Settings map under Workflows (Git & Source Control, Task Sources, Browser); Merge and cleanup; Checks. Together they form the full loop from idea to green CI without treating git as an afterthought bolted onto chat.
Troubleshooting common Source Control moments
If Send notes is blocked, check that an agent terminal is active and ready (not-ready, permission, or no-active-terminal states must clear first). If Create PR is disabled but visible, complete push or resolve the intent title/body requirements shown on the control. If Checks are empty, confirm the branch is pushed, integrations are connected, and a PR is linked or discoverable. If AI generation is missing, enable Source Control AI under Git & Source Control and ensure an agent is selected for that operation. If diffs look wrong, confirm you selected the correct worktree—parallel agents never share one dirty tree, so the “missing change” is often in a sibling workspace.
When something fails on the wire
Read the commit or push failure summary in Source Control. Use the matching AI recovery launch (commit failure fixes or push failure fixes) to hand the failure context to an agent in the same worktree. For CI, open the failing check detail and use broken checks fixes when you want automated triage. For merge conflicts, conflict resolution launch actions prepare the agent with the right prompt shape. For host review threads, review comment resolution keeps agent work aligned with reviewer feedback without manually pasting long threads into a blank terminal.
Source Control in Influxx is deliberately complete for the agentic loop—not a thin status badge. Stage and commit like a modern git client, annotate like a code review tool, talk to agents with line-accurate notes, open PRs with optional AI drafts, and watch checks until you are ready to merge. Master this panel and the rest of the cockpit—notes, agents, worktrees, and checks—locks into a single shipping habit you can repeat for every feature branch.
