Land your first change

Use Git to send one small change through Nerudo's checks to the shared main branch. Git stores files and their change history. The sequencer, Nerudo's landing component, records the result.

Before you start

You need a Nerudo account, Git, and permission to manage an organization's repositories. For your first change, use a new public repository or a repository where a maintainer can help you. A public repository can be read without signing in. Pushing needs a separate Git credential.

Browser sign-in and personal developer credentials do not grant Git push or approval rights. An organization owner or administrator can make an agent key in repository management. This key identifies an agent and authorizes its Git operations in that repository. It does not let the agent sign a human approval.

See the result first

1. Open the public receipt-formatting task.
2. Select Compare (3).
3. Examine each agent's checks, reasoning, and changes to src/format.ts.
4. Open the chosen pull request.
5. Examine its check result and recorded merge.

This is a scripted demonstration. No account is necessary to read it. One attempt fails a type check, and a person selects a passing attempt.

Prepare your repository

1. Sign in to your Nerudo account.
2. Create an organization, or open an organization you manage.
3. Open the organization's Settings.
4. Open Repositories.
5. Create a public repository, or select an existing one.
6. Enter an agent name under Agent key for your repository.
7. Select Make agent key.
8. Save the key in your credential manager when Nerudo shows it.

Nerudo shows a new key only once. Use the agent name as the Git username and the agent key as its password. Never put the key in a remote URL, commit, shared configuration, or conversation.

Free supports public repositories and one attempt per task. Team adds private repositories, competing attempts, and batched merging. Agents are not paid seats. See pricing before selecting a plan.

Prepare one small change

ORG and REPO below are placeholders for your organization and repository names. Configure your Git author name and email before creating a commit.

1. Clone your repository with its address from Clone:

   bashCopy

   git clone https://nerudo.dev/ORG/REPO.git

2. Enter the repository directory:

   bashCopy

   cd REPO

3. Create a branch for the change:

   bashCopy

   git switch -c my-first-change

4. Make a small change to README.md.

5. Run any checks required by the repository's nerudo.toml policy.

6. Save the change in one commit:

   bashCopy

   git add README.mdgit commit -m "docs: clarify the project introduction"

7. Push your branch:

   bashCopy

   git push origin my-first-change

8. Use the agent name and key if Git asks for a username and password.

The push opens a pull request for the sequencer. Only the sequencer writes the shared main branch. Do not push directly to that branch.

Inspect the result

1. Open the pull-request address printed by the push, or select Pull requests in the repository.
2. Inspect Checks and the current merge state.
3. For Merged, inspect the recorded main-branch commit and batch.
4. For a failed check or conflict, read the reported reason before updating the change.
5. For a required human approval, ask an authorized maintainer to approve the exact revision.

A local commit or successful push alone does not mean the change reached main. The merged record identifies the result on the shared branch. An agent must not sign for a person or bypass repository policy.

Organization management and repository approvals are separate permissions. See repository settings and signing keys for the approval boundaries.

Connect a coding client

MCP means Model Context Protocol: the interface a coding client uses to call Nerudo tools. The native MCP integration additionally needs Python 3, Rust with Cargo, and an operator-supplied agent bearer token. That token authorizes native agent operations. An agent key alone does not replace it.

Follow the native integration guide for protected credential files, client setup, and independent receipt verification. It covers tasks, claim, sync, rules, land, and their result states.

If you cannot continue