메뉴
When running Agentuity CLI commands for deploying, managing databases, creating sandboxes, configuring storage, queues, cron jobs, email, or any cloud resource. Also activates for SSH debugging, environment variables, and non-interactive automation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when building model-backed Agentuity features, AI routes, structured output, chat, streaming, tool calling, or app-owned state and memory. Covers plain server functions, AIGatewayClient, provider SDK choices, validation, KV-backed history, and safe tool execution.
Use when adding async jobs, queue workers, cron schedules, webhook ingestion, task tracking, long-running workflows, status polling, durable output, or idempotent background processing to an Agentuity app.
Use when working with the Agentuity CLI itself: installation, authentication, profiles, JSON output, command discovery, schema inspection, non-interactive automation, structured input, and deciding which Agentuity command family to use.
Use when managing Agentuity Cloud from the terminal. Covers deployments, deployment logs, environment variables and secrets, regions, project resource linking, cloud resource commands, SSH, SCP, monitoring snapshots, and agent-friendly CLI workarounds.
Use when adding relational data to an Agentuity app. Covers creating or linking managed Postgres, DATABASE_URL, pg, Drizzle ORM, pooling, transactions, migrations, safe parameter binding, and the narrow admin-script role for DBClient.
Use when adding Agentuity code to a framework app and choosing where routes, pages, server functions, config, or service clients belong. Covers Next.js, Nuxt, SvelteKit, Astro, Hono, React Router, Vite with React, and TanStack Start file placement.
| name | agentuity-ops |
| description | When running Agentuity CLI commands for deploying, managing databases, creating sandboxes, configuring storage, queues, cron jobs, email, or any cloud resource. Also activates for SSH debugging, environment variables, and non-interactive automation. |
| version | 2.0.0 |
agentuity <cmd> --helpagentuity ai schema showbun (never npm/pnpm) — check for agentuity.json or .agentuity/--region flags (~/.config/agentuity/config.json and agentuity.json)/home/agentuity (not /app)When running CLI commands programmatically (in Claude Code, CI, or scripts), skip confirmation prompts:
| Flag | Short | Behavior |
|---|---|---|
--confirm | -y | Skip confirmation prompts |
--force | — | Alias for --confirm (when command doesn't have its own --force) |
These work on any command with a confirmation prompt (deploy, create, delete, etc.).
Special cases:
agentuity project import — requires BOTH --name and -y (or --confirm) for non-interactive useagentuity cloud env push — has its own --force flag (overwrites remote values); --force does NOT alias --confirm hereagentuity cloud deployment remove/undeploy — has its own --force flag for the same reason| Purpose | Command |
|---|---|
| Create project | agentuity create |
| Start dev server | agentuity dev or bun run dev |
| Deploy | agentuity deploy |
| Check auth | agentuity auth whoami |
| List regions | agentuity region list |
| Get help | agentuity <command> --help |
| Full CLI schema | agentuity ai schema show |
| Migrate to v2 | npx @agentuity/migrate |
| Service | CLI Prefix | Documentation |
|---|---|---|
| KV Storage | agentuity cloud kv | https://agentuity.dev/reference/cli/storage.md |
| Vector Search | agentuity cloud vector | https://agentuity.dev/reference/cli/storage.md |
| Object Storage | agentuity cloud storage | https://agentuity.dev/reference/cli/storage.md |
| Sandbox | agentuity cloud sandbox | https://agentuity.dev/reference/cli/sandbox.md |
| Database | agentuity cloud db | https://agentuity.dev/services/database.md |
| SSH | agentuity cloud ssh | https://agentuity.dev/reference/cli/debugging.md |
| Deployments | agentuity deploy | https://agentuity.dev/reference/cli/deployment.md |
| Topic | Link |
|---|---|
| CLI Getting Started | https://agentuity.dev/reference/cli/getting-started.md |
| Build Configuration | https://agentuity.dev/reference/cli/build-configuration.md |
| Deployment | https://agentuity.dev/reference/cli/deployment.md |
| Local Development | https://agentuity.dev/reference/cli/development.md |
| Debugging | https://agentuity.dev/reference/cli/debugging.md |
| Storage Commands | https://agentuity.dev/reference/cli/storage.md |
| Sandbox Commands | https://agentuity.dev/reference/cli/sandbox.md |
| Configuration | https://agentuity.dev/reference/cli/configuration.md |
| Git Integration | https://agentuity.dev/reference/cli/git-integration.md |
| GitHub App | https://agentuity.dev/reference/github-app.md |
| Migration Guide | https://agentuity.dev/reference/migration-guide.md |
| Mistake | Better Approach | Why |
|---|---|---|
Blindly adding --region flag | Check config first | Region may already be configured |
| Using npm for Agentuity projects | Always use bun | Agentuity is Bun-native |
Hardcoding sandbox paths as /app | Use /home/agentuity | That's the default working directory |
| Making up CLI flags | Run --help first | Flags change between versions |
| Fabricating deployment URLs | Read actual output | URLs are generated dynamically |
Using expect/yes piping for prompts | Use -y or --confirm flag | Built-in flag support is cleaner and more reliable |
| Running v1 project without migrating | Run npx @agentuity/migrate first | v2 requires explicit agent/router wiring |
If you're unsure about any CLI command, flag, or service, check first rather than guessing:
agentuity <command> --help for flag detailsagentuity ai schema show