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

# CLI coding plan setup

> Choose a coding plan, finish checkout, and see what pays for your connected agents.

Choose a plan in the terminal, pay in your browser, then connect your agents.
This guide covers CLI 0.3.0.

## Choose how to pay

After you save sign-in in the full-screen app, **Payment method** asks:

> How will you pay?

The question appears once per workspace on this machine.
You must be able to manage its plan, sales must be open, and a fresh read must confirm no plan exists.
Shared-key sign-in does not show the question.

1. Use the arrows to select **Pay as you go** or **Coding plan**.
2. Press **Enter** to choose.
3. For **Coding plan**, select **Starter**, **Pro**, or **Team** at the displayed monthly price.
4. Press **Enter** to open checkout.
5. Finish payment in your browser.
6. Wait for confirmation, such as `Starter plan active. Your agents use it first.`
7. Press **Enter** to continue setup.

Prices come from the current workspace offer.
The monthly tiers are:

| Tier    | Monthly price (USD) |
| ------- | ------------------- |
| Starter | \$10                |
| Pro     | \$29                |
| Team    | \$99                |

The app says `Finish checkout in your browser.` and waits up to ten minutes for the plan to become active.
If the browser does not open, open the displayed link yourself.
Opening checkout alone does not activate it.

**Pay as you go** continues with credits.
**Esc** on the payment question also chooses pay as you go.
**Esc** while waiting continues setup without confirming a purchase.
You can buy later with `runinfra plan buy starter`.

## Existing plans and members

When sign-in finds an active plan, it shows the funding line instead of asking again.
For example: `Starter plan: your 5-hour window starts with your first request.`
Later, the line shows usage and reset time, credits, Standby, or the payment action needed.
Stale information includes its age.

Only an owner can buy or change a plan.
Browser and device approval list only workspaces you own.
Members can connect with a shared workspace key using `runinfra login --paste`.
That key follows the workspace plan unless it is marked **Credits only**.
Shared-key sign-in cannot buy a plan or open plan settings through CLI commands.
See [Sign-in and security](/docs/tools-sdks/connect-sign-in#review-the-workspace-and-permissions).

## Plan commands

| Command                     | Result                                                                           |
| --------------------------- | -------------------------------------------------------------------------------- |
| `runinfra plan`             | Show the tier, renewal, five-hour and weekly limits, resets, and funding policy. |
| `runinfra plan --json`      | Return the unchanged `runinfra.cli.plan/1` resource.                             |
| `runinfra plan buy starter` | Open Starter checkout. Replace `starter` with `pro` or `team` for those tiers.   |
| `runinfra plan settings`    | Open plan settings in the browser.                                               |

Without a plan, the CLI says `No coding plan on this workspace.`
While sales are open, it also suggests `runinfra plan buy <starter|pro|team>`.
Purchases and settings changes happen in the browser.
The CLI opens Billing for the signed-in workspace and the selected tier or settings action.
The command prints the address if you need to open it yourself, then waits up to ten minutes for a plan change.

When the browser launch succeeds, it says:

> Complete your plan change in the browser. Waiting up to 10 minutes. Press Ctrl-C to stop waiting.

| Exit  | Meaning for buy or settings                                                         |
| ----- | ----------------------------------------------------------------------------------- |
| `0`   | A plan change was confirmed. Run `runinfra plan` to inspect the resulting state.    |
| `3`   | Sign-in or plan management permission was refused.                                  |
| `4`   | Entitlement or plan refused, or the requested agent, key or resource was not found. |
| `5`   | Confirmation failed or no change was confirmed within ten minutes.                  |
| `130` | You interrupted the wait.                                                           |

**Ctrl+C** stops waiting without canceling the browser purchase or change.
Run `runinfra plan` to check again.
For exact failure messages, see [Plan and live usage messages](/docs/tools-sdks/connect-troubleshooting#plan-and-live-usage-messages).

## What pays now

Open `runinfra status` for live usage.
Its funding tile follows the workspace's current funding policy:

| Tile                      | What it shows                                                                             |
| ------------------------- | ----------------------------------------------------------------------------------------- |
| `plan`                    | Five-hour usage and reset time, or weekly usage before the first five-hour window starts. |
| `credits`                 | Available credits; estimated runway respects the remaining plan credit cap.               |
| `standby`                 | `chat, slower` and its refill time.                                                       |
| `plan` with `stopped`     | The next reset time, or `open Account` when an action is needed.                          |
| `plan` with `unavailable` | Plan information could not be read.                                                       |

Money totals count credit charges only.
The monitor states: `Money counts credits only. Plan use is in the plan tile.`
The connection receipt reports the actual payer for verification requests.

## Covered models and Credits-only keys

With a serving plan and a key that can use it, Connect selects covered, compatible chat models.
It also selects a covered starting model.
If the plan is serving but covered chat models cannot be confirmed, setup stops.
Without a serving plan, or with a pasted Credits-only key, the usual compatible model order applies.
Project settings can override an agent's starting model; follow its restart instructions.

Keys marked **Credits only** always need credits, even when the workspace has a plan.
At zero credits, connection or verification refuses with exit `4` and `This key is Credits only and the workspace has no credits.`
Add credits before retrying.

Rotate these keys in the dashboard to preserve their funding choice.
CLI rotation refuses with `Rotate this Credits-only key in the dashboard.` when credits are available.

Review shows what pays and the verification request count before you approve.
The CLI does not change your plan, credit fallback, or caps during connection.