NeuralCodeDOCS
Core workflow

Commit, push & merge

When you're happy with a workspace, ship it. The green Commit split-button is your hub for committing, pushing, opening a PR, or merging into the base branch.

2xlabs / fix-test-bug code-agents/fix-test-bug Ready to review Commit
The workspace header — status, the green Commit split-button with its dropdown, and Archive.

The Commit split-button#

The main button opens the commit dialog. Its dropdown holds every shipping action:

ActionWhat it does
CommitStage everything and commit with your message (or a default).
Commit & PushCommit, then git push -u origin <branch>.
Commit, Push & PRCommit, push, then open a pull request via gh pr create --fill. Requires the GitHub CLI & sign-in.
Merge into <base>Commit, then git merge --no-ff the branch into its base.

While any of these run, the button shows a spinner and a status label (Committing…, Pushing…, Opening PR…, Merging…), and the result streams into the git console.

The commit dialog#

Commit changes

Commit message
e.g. fix-test-bug
Leave blank to use the default. ⌘↵ to commit.
Cancel Commit
The commit dialog — pre-hinted with the workspace name; leave blank for a default.

Type a commit message, or leave it blank to use a sensible default. Press ⌘↵ to commit without reaching for the mouse. Committing stages all changes (git add -A) first.

Pull requests#

Opening a PR pushes the branch and runs the GitHub CLI to create a PR with an auto-filled title and body. On success the PR URL is shown in a toast. The PR action is only enabled when the GitHub CLI is installed and authenticated — see GitHub.

Merging#

Merge performs a no-fast-forward merge into the base branch, so your history clearly records that the workspace was merged. Afterwards the workspace is marked Merged; you can keep iterating or archive it.

Everything is real git
There's no magic — every action maps to ordinary git (and gh) commands run in your repo. You can always drop into the terminal and verify or take over manually.