# vibekoded

AI-first deployment instructions for vibekoded.

## Read this first

- Source of truth for AI agent behavior: https://vibekoded.app/llms.txt
- Humans should use the CLI flow on https://vibekoded.app
- AI agents should fetch this file before taking action:

```text
#fetch https://vibekoded.app/llms.txt
```

## Platform summary

vibekoded is a managed Kubernetes platform.

- Apps are deployed from container images.
- Each user has an isolated namespace.
- Public URLs follow: `https://<appname>-<short-namespace>.apps.vibekoded.app`
- API: `https://api.vibekoded.app`
- MCP endpoint: `https://mcp.vibekoded.app/mcp`
- Install script: `https://vibekoded.app/install.sh`

## Canonical CLI commands (human/operator path)

Use these command families only:

- `vk register|login|logout|status|activate`
- `vk app ...`
- `vk mcp ...`
- `vk account ...`

Quick CLI flow:

```bash
curl -fsSL https://vibekoded.app/install.sh | sh
vk register --email you@example.com --password yourpassword
vk activate
vk app ship myapp
vk app status
```

## MCP setup for AI clients

Preferred setup:

```bash
vk login --email you@example.com --password yourpassword
vk mcp create vscode
```

Other supported clients:

```bash
vk mcp create cursor
vk mcp create claudecode
vk mcp create codex
```

Manual fallback only when auto-setup is unavailable:

```bash
vk mcp show-config
```

## AI agent execution rules

1. Fetch this file first.
2. If using MCP, perform deploy/manage actions via MCP tools, not via CLI deploy commands.
3. Ensure the container image exists before `create_deployment`.
4. After deployment, call `get_dns` to return the live URL.
5. If auth fails, ask user to run `vk login` again and refresh MCP config/token.

## MCP tools (deployment core)

Primary tools:

- `create_deployment`
- `list_deployments`
- `get_deployment`
- `delete_deployment` (or `delete_app`)
- `get_dns`

Operational tools:

- `list_pods`, `get_pod`, `get_logs`, `delete_pod`
- `list_services`, `create_service`, `delete_service`

## Minimal AI deploy flow

1. Confirm user intent: app name, image, replicas.
2. Call `create_deployment`.
3. Call `get_dns`.
4. Report final URL and current deployment status.

Example MCP call:

```json
{
  "method": "create_deployment",
  "params": {
    "name": "myapp",
    "image": "registry.vibekoded.app/myapp:latest",
    "replicas": 1
  }
}
```

## Recovery playbook

- `401/403` auth errors: re-login with `vk login`, refresh MCP token/config.
- image pull/build issues: verify image exists and tag is correct.
- no DNS yet: retry `get_dns` after deployment becomes ready.

## Plans

- Free: one active app, short-lived deployments, full CLI and MCP onboarding.
- Pro: higher app limits, permanent deployments, app-level auto-redeploy controls.

Upgrade command:

```bash
vk account pro
```

Auto-redeploy controls (supported Pro apps):

```bash
vk app auto-redeploy status myapp
vk app auto-redeploy enable myapp
vk app auto-redeploy disable myapp
```