Create your first Agent Console job

In this quickstart, you create a manual Builder job that updates documentation in one repository and opens a pull request for review.

Before you start

You need:

An Account Admin role in Sidecar
Agent Console enabled for your workspace
A connected GitHub or GitLab repository where you can safely make a documentation change
Permission to review pull or merge requests in that repository

If the repository is not connected, complete Connect repositories first.

Create the job

Open Builder

In Sidecar, select Agents, then select Builder.Builder does not ship with presets, so you create this job from scratch.

Builder agent page with the New job button — Open Builder, then click New job.

Start a new job

Click New job.Enter these values:

Setting	Value
Name	`Update repository documentation`
Description	`Correct one small documentation issue and open a pull request.`
Instructions	Use the example below.
Repositories	Select one repository.
Delivery	Open a pull request
Trigger	Manual

Review the repository documentation for one small, clearly incorrect or
outdated statement. Correct it, preserve the existing style, and validate
any affected links or formatting. Do not change application code.

Selecting one repository keeps the first run focused. An empty repository selection means all currently accessible repositories.

New Builder job populated with documentation instructions and one selected repository — Populate the job and select one repository for the first run.

Create the job

Click Create job. Sidecar opens the job configuration page.

Review the job settings

Confirm these settings before the first run:

Scope contains only the repository you selected.
Completion and output is set to Open a pull request.
Schedule and trigger is set to Manual.
MCP servers can stay at its default. This task does not require an MCP server.
Tool permissions is set to Autonomous.

Autonomous mode lets gateable tools run without pausing. Core repository tools are always available. You can use Supervised for later jobs when you want gateable web or MCP tools to require Account Admin approval.

Builder job configuration with repository scope, Manual trigger, MCP server selection, and Autonomous permissions — Review the job's scope, trigger, MCP access, and tool permissions before running it.

Run the job

Click Run now.Sidecar opens the run detail page. The run moves from Queued to Running while Builder reads the repository, makes the change, and validates it.

Running scheduled Builder job with its first turn visible — The run detail page updates while Builder is working.

Review the result

When the run finishes, open its artifact. Review the pull request and its checks before merging.Builder never merges its own changes.

Succeeded Builder run with a pull request artifact and final answer — Open the source-control artifact when the run succeeds.

Next steps

Learn how to create jobs from presets.
Connect an MCP server, then give an agent access.
Create a schedule for recurring work.
Run an agent from Slack for an ad hoc request.

​Before you start

​Create the job

​Next steps

Before you start

Create the job

Next steps