AI CodeOps

Sessions

Start an AI session in AI CodeOps: describe the task, pick a project and workflow, watch the agents work live, review the diff, and open a pull request.

A session is one piece of AI work on a project. You describe a task; a team of agents plans it and writes the change, your tests run on it, and the agents then review what was written. You then review the result and decide whether it ships. Everything runs on the platform; you watch it in the browser.

Start a session

  1. Open Develop → AI Sessions and choose New session.
  2. Fill in the Start an AI session form (fields below).
  3. Choose Start session. The session is queued and appears in the list.

The form's fields:

  • What should the session do? Describe the task in plain words, for example "Add rate limiting to the public API and write tests for it."
  • Workflow: how the agents should work. The default, Plan, Build, Review & Test, suits most changes. See Agents and workflows.
  • Project: required. AI-generated code always belongs to a project.
  • Model tier or Model: which models to use. See Models and tiers.
  • File context (optional): comma-separated paths the agents should read first.

You can also start one from a project's page with Run workflow.

How large a change can be

A session's change has to be small enough for a person to review:

  • its diff can be up to 60 KB;
  • it can change up to 25 files, each up to 64 KB.

A larger change is refused whole, never cut: the session ends with "The change is too large to review", and names the files most of the size is in. Split the task into smaller ones.

A session rewrites each file it changes in full, and it is shown only the start of a long file. A rewrite that would drop lines it never saw is not written: the session is given those files whole and tries once more, and if the result still drops them the session ends with the reason. Then ask for a narrower change, or name the part of the file to change.

Watch it live

The session page updates as it runs. You see each step (which agent, what it is doing, its status), and the session's cost and tokens as they accrue. The list under AI Sessions shows every session with its project, duration, cost and status, and badges for sessions that produced changes or findings.

To stop a session, choose Cancel session and give a reason. The reason is saved on the session and shown on its page.

Review the result

When the session finishes, its page shows:

  • Summary: what the agents did, in the last step's words. When the workflow has steps that follow the code, such as Review and Test, it is written after your tests ran. If what it says about tests contradicts the recorded result, a warning above it says so.
  • Proposed changes: the diff, with a .patch download. If your request named files and the change left some of them alone, a note lists them.
  • Quality gates: test results and whether the change is release-ready. See Quality gates.
  • Findings: issues the review found, with severity and file.

Every session that writes code is also listed under Develop → Changes, where you can follow it from proposal through review, merge and deployment.

Ask for changes

Use the Follow-up prompt box on the session page to ask for refinements or a next task that builds on this one. Choose Send follow-up; it continues from the session's context. The follow-up's page shows the original Task and, under it, Latest request (follow-up N). While a session is still running, a follow-up starts a new, linked session; the running one carries on unchanged.

Re-run starts the same task again from the beginning.

Approve and open a pull request

A session that changes code opens a review on Review & Gate → Approvals. On the session page, choose Accept changes or Reject. The person who launched the session can't approve it if someone else in the workspace can. See Approvals and policies.

Once the change is approved and passes its quality gates, AI CodeOps opens the pull request for you: a new branch codeops/run-<id> in the project's repository, into its default branch. You can also choose Create Pull Request yourself. The button explains what's missing if it's locked, for example Connect git to open PR or Add a repository to open PR.

Nothing merges without your approval.

Terminal

Develop → Terminal (beta) opens a shell at a project's root in its own isolated sandbox, for when you want to look around or run a command yourself. Commands never run on the platform's own servers. Availability depends on your plan.

Next steps

Frequently asked questions

Do I need to install anything to run a session?

No. Sessions run in the cloud and you follow them in the browser. There is no CLI or local setup.

Can I change a session's result before approving it?

You can ask for changes with a follow-up prompt. Editing the change after it was approved resets its approval, so it has to be approved again.

Was this page helpful?