# Nests Agent Guide

Use this guide when the user asks you to continue from Nests, mentions a
Nests link, asks about agent handoff, or starts cold in a repo that may have
Nests installed.

## First Action

Run:

```bash
nests status
```

Then follow the status output.

If Nests reports a newer or discovered remote:

```bash
nests pull
```

If Nests reports no accessible Nest and the user wants to create one:

```bash
nests init
```

## Read Context

After status or pull:

```bash
nests context --for codex
```

Use `--for claude` when operating inside Claude Code. Use `--for agent` for a
generic harness.

## Work Rules

- Continue from the handoff when it exists.
- Verify agent claims against diffs, files, command output, and artifacts.
- Keep claims separate from evidence.
- Use the project test and lint commands before claiming completion.

## Record Progress

```bash
nests report "<what changed>"
nests artifact add <path>
```

## Hand Off

```bash
nests snapshot -m "<summary>"
nests share
```

Use `nests share` when another device, harness, or human needs a link.

## Link Handling

If the user provides a Nests link, pull it directly:

```bash
nests pull <link>
nests context --for codex
```

Do not assume the local repo has the latest memory until `nests status` agrees.