Docs / Git
  1. Docs
  2. Using Arcon

Git from your phone

When an agent changes code, you can review it and ship it without opening a laptop: see the diff, commit, push, open a pull request, follow its checks, and go back to a checkpoint if a step went wrong.
4 min read Video · 0:50

Git from your phone0:50

Review changed files and diffs, commit with your own or an agent-written message, push, open a pull request, ask the agent to fix failing CI, and go back to a checkpoint.

Show transcriptHide transcript

When an agent changes code, you can review it and ship it without opening a laptop.

See the branch, what changed, and by how much: every file, with its additions and deletions. Tap a file for the full diff.

Commit with your own message, or let the agent write one. Then push, and open a pull request.

Pushing to the base branch needs your confirmation, and nothing is ever force-pushed. Arcon follows the pull request’s checks.

If CI fails, ask the agent to fix it. It gets the failing log.

Checkpoints save private snapshots on your computer, so you can go back to the moment before a risky step. Ship from anywhere. Arcon.

See what changed

Open a session and tap its branch chip. You see the branch, and every changed file with its additions and deletions. Tap a file for the full diff. In the Windows app, a session’s Changes tab does the same (J / K move between files, [ / ] between hunks).

Commit

Commit with your own message, or let the agent’s fast model write one from the diff. Choose which files go in, or take them all.

Push and open a pull request

  • Push sends the branch to its remote. Pushing to the base branch (main or master) needs your explicit confirmation.
  • Nothing is ever force-pushed.
  • Open a pull request with a title and a description, as a draft if you like, against the remote’s default branch or one you choose.

Checks and CI fixes

Arcon follows the pull request’s checks. If CI fails, ask the agent to fix it: it gets the failing log to work from.

Checkpoints

Checkpoints are private snapshots of the working tree, saved on your computer (never pushed). Take one before a risky step, and restore it to go back to exactly that moment.

From the terminal

The same actions work from any terminal, for the session in the current folder or any other:

Terminal
arcon git statusarcon git diff src/api/cart.tsarcon git commit --ai                 # the fast model writes the messagearcon git push                        # add --confirm-base to push main/masterarcon git pr create --title "Fix the flaky cart test" --draftarcon git pr ci-fix                   # ask the agent to fix failing checksarcon git checkpoint "before the migration"arcon git restore <id>

Worktree sessions finish with arcon git worktree merge, pr or discard --confirm. Every flag is in the CLI reference.

Written for connector 0.12.0 and the current apps.Something unclear or wrong? Tell us