> ## Documentation Index
> Fetch the complete documentation index at: https://docs.checkfu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Checkfu with your coding agent

> Load version-matched recipes and the Agent authoring skill without granting a coding agent a second mutation authority.

The CLI ships two kinds of coding-agent context:

* **Recipes** explain how to build customer-owned integration code from tested examples.
* **The authoring skill** explains how to inspect, compile, and evaluate a Checkfu Agent project.

Both version with the installed CLI. Neither grants a coding agent authority to mutate Checkfu, own desired configuration, execute a Session, or handle credentials.

<Warning>
  The Checkfu CLI has no self-service public installation channel during private alpha. The commands below require a source checkout or an explicitly authorized alpha artifact. Read [CLI access](/getting-started/cli-access) first.
</Warning>

<Warning>
  This flow runs from a Checkfu source checkout.
  Part of this flow is behind a rollout fence; a deployment that has not enabled it refuses the request rather than running it.
  Confirm [capability status](/getting-started/status) before making availability part of your application's contract.
</Warning>

## Print an integration recipe

List the embedded catalog:

```sh theme={"theme":{"light":"github-light","dark":"github-dark"}}
checkfu add --list
```

Print one recipe or pipe it to a coding agent you already control:

```sh theme={"theme":{"light":"github-light","dark":"github-dark"}}
checkfu add tool-server
checkfu add embed | claude
```

The recipe command writes nothing, fetches nothing, and invokes no agent. Each recipe declares the example files it quotes. Repository checks fail when a source disappears, a quoted excerpt drifts, a required CLI command leaves help, or a required SDK symbol leaves the built types.

A recipe is not desired state. Your coding agent may edit your application after you choose to run it, but the recipe never claims a Checkfu resource.

## Install the authoring skill

Install the shipped `checkfu-agent-authoring` skill into a supported user-level layout:

```sh theme={"theme":{"light":"github-light","dark":"github-dark"}}
checkfu skills install --client claude
checkfu skills install --client codex
```

Use an explicit directory for another client:

```sh theme={"theme":{"light":"github-light","dark":"github-dark"}}
checkfu skills install --client generic --dir ./agent-skills
```

An identical installation is a no-op. The installer refuses a modified, missing, extra, or symlinked installed file rather than overwriting it. Review or move a local copy before installing a different version.

The skill routes the coding agent to:

1. `checkfu agent info . --json` before edits;
2. the closed project paths under `checkfu.json`, `agent/`, and `scenarios/`;
3. `checkfu agent compile .` and inspection of `.checkfu/current.json`;
4. `checkfu eval .` and the closed observation format; and
5. the rule that `.checkfu` evidence is not committed or uploaded without explicit authorization.

The skill does not carry an API key. It does not call `agent apply`, remote Agent mutations, MCP tools, or Session operations by itself.

## Keep authoring authority explicit

A coding agent edits candidate source. A Git commit, pull request, local plan,
or proposal does not reserve a Checkfu resource. Repository CI owns review and
merge policy for ordinary Agent authoring.

Use canonical Agent operations for direct changes, or run `checkfu agent plan`
and `checkfu agent apply` on a checked-in Agent project. Those commands write
Agent configuration only. Budgets, grants, Connections, Automations, and Memory
are created through their own operations.

Follow authorization and concurrency errors through the supported resource
workflow. Retrying through SDK, CLI, or MCP grants no additional authority.
See [Authoring authority](/concepts/agent-blueprints#authoring-authority).

## Recipe or Agent project?

| Surface | Job | Changes Checkfu by itself? | Runtime authority |
| - | - | - | - |
| Integration recipe | Build customer-side adapter, tool server, or UI code | No | None |
| Agent project | Human-readable local source, compilation, and evaluation | No | None |
| MCP | Discover and call served canonical operations | Only when the selected tool is authorized | None |

Use a recipe for code that stays in your stack. Use an Agent project for desired Agent configuration. Use MCP only as another authenticated interface over the served public contract.

Continue with [Author an Agent project](/guides/author-an-agent-project) for the human workflow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.