Auto commit

Commit in one click

In the Changes view of the Git panel, the ✦ button left of Commit runs Auto commit. It:

• stages every change, untracked files included;
• sends the staged diff to Codex, which writes the message;
• creates the commit on the current branch.

Meanwhile the button spins: “Auto commit in progress…”. The message follows the style picked in Settings; the commit conventions in the AGENTS.md at the repository root come first, and an AGENTS.override.md comes before the AGENTS.md.

Pick the message style

Open Settings > AI, Commit messages card. Default style offers three styles, with an example under the choice:

• Imperative: one short line, verb in the imperative;
• Conventional Commits: type and optional scope prefix, readable by changelog tools;
• Subject + body: short subject, then a brief paragraph explaining why.

The same card sets the Model used for generation and Fast mode: faster replies, higher usage. Reasoning effort stays low.

Install Codex

Codex writes the message: it must be installed on this computer, even for a WSL or SSH project. Settings > AI shows its state, Installed with its version or Not installed, and offers the update when a newer version exists.

If Codex is missing, Auto commit changes nothing: “Codex is not installed. Install it from Settings > AI to generate the commit message.” If it fails along the way, staged changes are kept: try again, or commit with your own message.

Codex runs without asking for approval, but read-only, with no shell, no web search and none of your configuration: all it can do is write the message.

Stage and commit yourself

Each file has its buttons: Stage or Unstage, and Discard changes…. Group headers offer Stage all, Unstage all and Discard all changes…. Before discarding, Soreno backs the files up in a Git stash, to be recovered with Git outside Soreno.

Commit opens the Commit message. Write it, or click Generate message: Codex gets the staged diff and the project’s commit instructions, without creating a commit, and you read it over before confirming with Commit. Only staged files go into the commit.

During a merge, the button becomes Commit merge, with the merge message already filled in.

Push and pull

At the top of the file list, the branch shows with its upstream, and one button depending on the state:

• Publish: the branch has no upstream yet;
• Push, followed by the number of commits to send;
• Pull, followed by the number of commits to fetch; if the branches have diverged, it runs a Pull with rebase;
• Up to date: nothing to send or fetch.

The Fetch button next to it updates the remote’s state. More actions holds Pull, Pull with rebase and Push, and the Remote repository choice when the project has several.

When the commit is blocked

• nothing is staged: Commit stays greyed out, stage files first;
• detached HEAD: the panel creates no commit, create or switch to a branch in Branches;
• conflicts: resolve them, then Mark resolved…, before committing;
• no author set: Soreno asks for an Author name and an Author email, for this repository or, with Use for all repositories, for all of them; saving doesn’t retry the commit.