v1.7.2

Agent runs that look like your own work, and a page for each one

v1.7.2 is about what an agent run leaves behind on GitHub and what you can see of it afterwards.

Commits and pull requests in your name

A run's commits are now authored as the person who asked for it, with their GitHub name and noreply address, and siGit Code as co-author. The pull request is still opened by the App as a draft, because GitHub does not let you approve a pull request you opened yourself, and it is assigned to the person who asked. Its title comes from the issue's title instead of the first line of the prompt.

A run nobody can be named for is authored as siGit Code <noreply@sigit.si>.

Base branch and branch name follow the repository

A new run used to start from the default branch on a sigit/ branch, whatever the repository's own practice was. It now goes by the first of these that answers:

  1. [pull_request] in the repository's settings file.
  2. What the repository's recent pull requests from people do: the base most of them target, and the prefix most of their branches carry. A task that reads like a fix gets the repository's fix prefix where it has one.
  3. The default branch and a sigit/ prefix.

A settings file for the run

A repository can shape its runs with .sigit/code-cloud-agent/config.toml on the default branch: which directories of the runner the agent can see, extra PATH entries, plain environment values, setup commands to run before the agent starts, how many rounds of tool calls a run may make, and the base branch and branch prefix above. A key the file does not know stops the run with the reason, so a typo is not silently ignored. The keys are in the agent documentation under "Customizing a run".

The agent reads the conversation

The prompt now includes the issue's or pull request's comments, and the review comments on a pull request, marked as background written by other people. Until now the agent saw the issue body and the comment that mentioned it and nothing in between.

A run that only reports is not a failure

A run that ends with a summary and no commits used to be marked failed with "finished without producing any commits". It now completes, and the summary is posted as the reply. A run with no commits and nothing to say still fails.

A run that exits with an error or runs out of time now says so on the issue. Before, the mention got an acknowledgement and then nothing.

siGit Code in the account menu

"siGit Code" in the account menu lists the runs you started, at /code/runs. Each run has a page with what was asked, how it ended, the Actions run and the transcript. The page opens only for the person who asked.

Everything the agent posts on GitHub now ends with one line that says what wrote it, who asked, and links to that page.

Repository pages

The repository's CI/CD page moved from /ci-cd to /cicd, and the Sessions tab is now "Cloud Agent" at /scca. The old addresses redirect. Cloud Agent threads are shown to the repository's owner or the organization's members; everyone else sees a page that explains what it is.

The agent App reads code

The agent's GitHub App now asks for read access to Contents. Without it GitHub refused to open a pull request from a branch the App could not read. Installations need to accept the updated permission once.


Release masters: @setoelkahfi and @sigit.