---
title: Coding-agent plugin
description: Give Claude Code or Codex Croche skills, then ask it to build your app.
---

[!nav:main](/nav/main.md)

The Croche plugin gives Claude Code and Codex focused skills for integrating the SDK and using the CLI. The skill helps your existing coding agent use Croche; it does not define or replace the agent. Installing the plugin alone does not install the SDK or CLI; the coding agent handles those installs as part of the requested integration, with the appropriate permissions.

## Install the plugin

Use the public [H1R-AI/croche marketplace](https://github.com/H1R-AI/croche).
Run the commands for your coding agent in your terminal:

**Claude Code**, in your terminal:

```sh
claude plugin marketplace add H1R-AI/croche
claude plugin install croche@croche
```

**Codex**, in your terminal:

```sh
codex plugin marketplace add H1R-AI/croche
codex plugin add croche@croche
```

> TODO verify: complete both installation workflows against the public `H1R-AI/croche` marketplace, including loading the installed skill. Public marketplace availability is not yet confirmed. Do not substitute a private source repository if installation fails.

## Without plugin support

Copy all five complete skill folders from the public distribution's `skills/` directory: **`croche`**, **`croche-cli`**, **`croche-config`**, **`croche-platforms`**, and **`croche-troubleshoot`**. Keep each folder's `SKILL.md`, `references/`, and `agents/` together.

| Agent | Scope | Destination directory |
| --- | --- | --- |
| Claude Code | This project | `.claude/skills/` |
| Codex | This project | `.agents/skills/` |
| Codex | Your projects | `~/.codex/skills/` |

For example, the core entrypoint becomes `.agents/skills/croche/SKILL.md` and config guidance becomes `.agents/skills/croche-config/SKILL.md`. Do not flatten the folders, copy only the core, or nest an extra `croche/` directory. Review any existing skill before replacing it.

> TODO verify: the published five-skill distribution and discovery in each destination above, including the user-level Codex path for the installed version. Prefer project-local installation while that check is pending.

## What the skill helps with

| Developer task | Croche guidance |
| --- | --- |
| Add an agent to an app | Choose the SDK, open a project, and send a first message |
| Add app actions | Declare tools, register handlers, and keep authorization in app code |
| Build a conversation UI | Use message events and separate agent conversations |
| Edit app configuration | Use the CLI to read and save a draft, then test through the SDK |
| Inspect an integration | Check project usage, app-verification settings, and available local debugging commands |

With the plugin installed, start in an empty or existing app repository and say:

> Build this with Croche.

“Use Croche” or “Croche로 개발해줘” should trigger the same core skill. In an **empty repo**, it asks **what the app should do and for the human login setup in one combined request**, without repeating a purpose you already supplied. In an **existing app**, it infers the purpose and stack and asks **only for the human login setup**. That setup is signup, one developer key, and user-run `croche login` after the agent installs the CLI. It does not ask you for a service endpoint, project key, SDK debug key, stack, project name, or persona. It handles the project, private debug-key file, SDK, code config, code and first-turn check; required permissions still apply.

This workflow is the target acceptance check for **both Claude Code and Codex**, not a claim that either installation or the planned CLI has already been release-verified.

The plugin supplies Croche-specific instructions when working on a Croche integration. The commands your coding agent runs are the `croche` commands in the [CLI guide](cli.md), not a separate set of app-action commands invented by the plugin.

## Prepare your account; let the agent do the setup

Your only setup is to sign up in Studio, create one developer key under **Account → CLI keys**, then run `croche login` in any private terminal on the same machine and OS account as the agent. Paste the key into its hidden prompt, never into chat. The agent installs the CLI first but **never runs login**. See the [quickstart](quickstart.md); the login workflow is pending release verification.

The agent installs the required SDK and CLI with the appropriate permissions, runs `croche projects create`, then uses the **planned** `croche debug-keys create --project PROJECT_ID` command. That command writes the debug key to a private `.env` file and prints only metadata. The agent prepares the code and verifies the first reply without exposing either secret. The new CLI command/file behavior and published SDKs still require release verification.

Review state-changing actions and never let the agent force-overwrite an existing debug key without approval. Production config approval remains a separate developer action in Studio. The plugin itself does not automatically install packages or grant account access; it guides the coding agent's work.