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

# Agentic Development

> Use the Para CLI with Claude, Codex, and other coding agents

export const Link = ({href, label, newTab = false}) => {
  const [isHovered, setIsHovered] = useState(false);
  return <a href={href} target={newTab ? '_blank' : '_self'} rel={newTab ? 'noopener noreferrer' : undefined} className="not-prose inline-block relative text-black font-semibold cursor-pointer border-b-0 no-underline" onMouseEnter={() => setIsHovered(true)} onMouseLeave={() => setIsHovered(false)}>
      {label}
      <span className={`absolute left-0 bottom-0 w-full rounded-sm bg-gradient-to-r from-orange-600 to-purple-600 transition-all duration-300 ${isHovered ? 'h-0.5' : 'h-px'}`} />
    </a>;
};

Use the Para CLI with Claude, Codex, Cursor, Windsurf, and other coding agents to manage project setup, API keys, and integration checks from the terminal.

## What You'll Learn

* How to give an agent a safe Para CLI workflow
* Which CLI commands are useful for setup, key management, and diagnostics
* How agents can inspect the command catalog instead of guessing command syntax
* Which operations should require your approval before the agent runs them

## Start With CLI Context

Install and authenticate the CLI before asking an agent to configure Para:

```bash theme={null}
npm install -g @getpara/cli
para login
para whoami
```

Then let the agent inspect the machine-readable command catalog:

```bash theme={null}
para commands --json
```

The catalog includes command paths, arguments, options, JSON support, interactivity, side effects, and examples. Agents should use it before running unfamiliar `para` commands.

<Info>
  For broader Para context, give your agent the <Link href="/v3/developer-tools/ai-tooling/agent-skill" label="Para Agent Skill" /> or connect the <Link href="/v3/developer-tools/ai-tooling/mcp" label="Para Docs MCP" />.
</Info>

## Prompt Claude or Codex

Use a prompt that gives the agent a clear boundary:

```text theme={null}
Use the Para CLI to help me finish my Para integration.

First run read-only commands:
- para commands --json
- para auth status --json
- para whoami --json
- para keys list --json
- para keys config show --json

Then propose the exact commands needed to configure my local app.
Ask before creating, rotating, archiving, or changing API keys or projects.
Do not print secret keys in the chat unless I explicitly ask.
```

For a new Next.js app, ask for a full setup path:

```text theme={null}
Use the Para CLI to scaffold a Next.js app with EVM and Solana support.
After scaffolding, connect it to my selected Para project, write the API key to the app env file, and run para doctor on the result.
Use JSON output where available and explain any command that needs my approval before running it.
```

For an existing app, ask the agent to inspect first:

```text theme={null}
Use the Para CLI to audit this existing Para integration.
Run para whoami, para keys config show --json, and para doctor.
Compare the API key config to the app's env vars and provider setup.
Recommend fixes before changing files or API key configuration.
```

## Common Agent Workflows

### Confirm Context

```bash theme={null}
para auth status --json
para whoami --json
para orgs list --json
para projects list --json
para keys list --json
```

Use these commands before any mutation so the agent knows which organization, project, and key environment are active.

### Save Project Defaults

```bash theme={null}
para orgs switch <org-id>
para projects switch <project-id>
para init --yes
```

`para init --yes` writes `.pararc` for the current directory using the resolved org, project, and key environment. Commit `.pararc` only if your team wants shared project defaults, and never store secrets in it.

### Manage API Key Settings

```bash theme={null}
para keys config show --json
para keys config security --origins "https://app.example.com,http://localhost:3000"
para keys config auth --oauth-methods "GOOGLE,APPLE"
para keys config setup --wallet-types "EVM,~SOLANA"
para keys config webhooks --url "https://api.example.com/webhooks" --events "user.created,wallet.created" --enabled
```

Use category commands for focused changes. Most `para keys config` category commands can run interactively or with flags.

### Diagnose an Integration

```bash theme={null}
para doctor
para doctor --json
para doctor --category configuration
para doctor --severity error
```

Agents can use `para doctor --json` to identify missing env vars, framework-specific setup issues, API key mismatches, duplicate modal instances, package issues, and other integration problems.

## Use JSON Safely

Many commands support `--json` for agent and CI workflows. Some commands require enough non-interactive flags before JSON output is allowed:

| Command                              | Required for non-interactive JSON                                                   |
| ------------------------------------ | ----------------------------------------------------------------------------------- |
| `para init --json`                   | Add `--yes`                                                                         |
| `para create --json`                 | Provide an app name plus `--networks` for Next.js or `-t expo --bundle-id` for Expo |
| `para projects create --json`        | Add `--name`                                                                        |
| `para projects archive --json`       | Add `--yes`                                                                         |
| `para keys create --json`            | Add `--name`                                                                        |
| `para keys rotate --json`            | Add `--yes`                                                                         |
| `para keys archive --json`           | Add `--yes`                                                                         |
| `para keys config <category> --json` | Provide at least one category flag                                                  |
| `para update --json`                 | Add `--check` or `--yes`                                                            |

<Warning>
  Treat key rotation, key archival, project archival, migration apply, rollback apply, and CLI updates as approval-required operations. They can change live configuration or local files.
</Warning>

## Keep Secrets Out of Chat

* Prefer `para keys get --copy` when you need the public API key locally.
* Use `para keys get --copy-secret` only when you intentionally need the secret key.
* Avoid pasting secret keys into an agent conversation.
* Ask the agent to summarize configuration without printing full secrets.

## Useful Links

* <Link href="/v3/cli/installation" label="Install and configure the CLI" />
* <Link href="/v3/cli/commands" label="CLI command reference" />
* <Link href="/v3/general/developer-portal-setup" label="Get your API key" />
* <Link href="/v3/developer-tools/ai-tooling/agent-skill" label="Agent Skill" />