Agentic coding

Your coding agent already knows Volcano

One command briefs Cursor, Claude Code and Codex on how a Volcano project is shaped, then keeps production behind an explicit confirmation.

Start building
volcano setup
volcano setupdetected      cursor · claude-code · codexcursor        [updated]    11 skills · 4 files changedclaude-code   [updated]    0.2.14 → 0.2.16  (restart your agent to apply)codex         [installed]  (restart your agent to apply)# re-run any time; each run lands on the latest skills✓ your agents now build against the real command surface
Overview

The model is fine. The context is missing.

An agent in your editor will invent a CLI flag, a config key, or an SDK method that never existed, and you find out at deploy time. It is not writing bad code — it is writing code for a platform it has never been told anything about, from a training set that predates yours.

So fix the input. volcano setup installs Volcano's instruction file and eleven skills into the agents you already run, which turns guesses into lookups: the real project layout, the real deploy contract, the SDK's own type definitions, and a safety model that keeps your cloud project out of reach until you explicitly ask for it.

Setup

It installs into the agents you already run

One command finds the coding agents on your machine and sets each one up. Claude Code and Codex get Volcano through their own plugin marketplace; Cursor, opencode and pi get the skills written into their skills directory. When nothing is detected, a manual install drops them under ~/.volcano instead.

  • Cursor, Claude Code, Codex, opencode and pi
  • --dry-run reports the changes and writes nothing
  • --yes for a non-interactive run inside CI or an agent
volcano setup --dry-run
cursor        [current]    11 skills · nothing to writecodex         [outdated]   marketplace plugin behind latestopencode      [installed]  would write 11 skillsDry run: nothing was written.
Grounding

Eleven skills instead of a plausible guess

The skills carry the parts an agent cannot infer: how a project is laid out and deployed, and what the SDK actually exposes. One rule in the instruction file removes most of the remaining waste — check volcano <area> --help before inventing a flag.

  • volcano-platform: project shape and the deploy contract
  • volcano-typescript: the SDK's own type definitions
  • volcano docs mcp answers questions from the real docs
~/.cursor/skills
volcano-platform    volcano-sdk         volcano-typescriptvolcano-auth        volcano-database    volcano-functionsvolcano-storage     volcano-realtime    volcano-nextjsvolcano-error-handling                  install-volcano# AGENTS.md sits alongside them as the entry point
Guardrails

It cannot ship to production behind your back

Building, running and deploying locally happen without interruption, because local mode only ever targets localhost:8000. Everything that touches your cloud project is confirm-first, and the agent cannot even sign you in — a device code has to be approved by a human with a browser.

  • Local deploys are automatic; cloud deploys never are
  • Deletions, secrets and domain changes ask first
  • No agent can approve a volcano login device code
the local loop, unattended
volcano startvolcano functions deploy --allvolcano functions invoke create-order --json{ "statusCode": 201, "orderId": "o_4f2a" }# localhost:8000 throughout — production was never touchedNext: deploy to the cloud with volcano cloud functions deploy --all
Path to production

How it works

  1. 01

    Brief your agent

    volcano setup finds Cursor, Claude Code, Codex, opencode or pi and installs the skills into each one. The two that use a plugin marketplace pick them up after a restart.

  2. 02

    Let it scaffold

    The agent runs volcano init first, because every deploy command expects that layout. Templates cover JavaScript, Next.js, Python and Ruby.

  3. 03

    Prove it locally

    volcano start brings up the local environment, the agent deploys into it and invokes what it wrote, then reports the result. No cloud credentials needed.

  4. 04

    Ship it yourself

    volcano login, pick the project with volcano use, then run the cloud deploy. The agent suggests the command; you are the one who runs it.

Code

From a fresh machine to a deployed project

Shell
# Detect every coding agent on this machine and set each one up volcano setup # Look before you leap volcano setup --dry-run # Or target just one: claude-code, codex, cursor, opencode, pi volcano setup --harness claude-code # Non-interactive, for CI or for an agent running the command itself volcano setup --yes # Re-running is the update path. Each agent reports one of # [installed], [updated] or [current], and marketplace plugins # show the version delta they moved through.
Return

What briefing the agent saves

One commandto brief every agent

volcano setup detects the coding agents you have and installs into all of them, then keeps them current on re-run.

11 skillsof real API surface

Project shape, the deploy contract and the SDK's own type definitions, versioned in one place instead of recalled from memory.

Zerounattended production deploys

Cloud deploys, deletions, secret changes and visibility changes are confirm-first, with no exceptions.

What you get

Less rework

The commands and methods it reaches for are ones that exist.

Safe to let run

The unattended loop is local only, and stops at your cloud project.

Current by default

Re-running setup lands every agent on the latest skills.

Platform

Built on Volcano

Functions and agents

  • Functions

    What the agent writes and deploys first: handlers that see the caller's verified identity and scale to zero.

Databases and vector

  • Postgres databases

    Migrations are plain SQL files the agent can read and review, with policies rather than a generated access layer.

Next.js frontends

  • Next.js hosting

    volcano init nextjs scaffolds it and one deploy command puts it on a global CDN with TLS.

Authentication

  • Authentication

    Sign-in is configuration, not a service the agent has to wire: providers and token lifetimes sit in volcano-config.yaml where you can review the diff.

Frequently asked questions

Read the docs
Which editors and agents are supported?

Cursor, Claude Code, Codex, opencode and pi. Claude Code and Codex install through their own plugin marketplace; the rest have the skills written into their skills directory. If none is detected, volcano setup --manual puts the skills and AGENTS.md under ~/.volcano so any agent can read them. There is no VS Code extension and no JetBrains plugin.

Do I have to install a plugin by hand?

No. volcano setup does the detection and the install. For Claude Code and Codex it adds the Kong/volcano-agentic-plugins marketplace and installs the volcano plugin from it, which loads once you restart the agent.

Can the agent deploy to production on its own?

No, and that is deliberate. The instructions it follows say never to auto-deploy to the cloud, so every volcano cloud command needs your explicit go-ahead — as do deletions, secret changes, visibility changes and anything billing-related. What it will do unprompted is the local equivalent, which only ever targets localhost:8000.

How does the agent sign me in?

It doesn't. volcano login is an OAuth device-code flow: the CLI prints a code and a URL, then polls while a human approves it in a browser. Agents are told not to look for tokens on disk or try to approve a code programmatically. For CI, where no browser exists, set VOLCANO_TOKEN instead.

Is there an MCP server?

Two. volcano docs mcp serves the documentation over stdio as volcano-docs with docs_search, docs_get and docs_list. The hosted server at api.volcano.dev/mcp gives an agent a scoped tool surface over one project, authenticated with a project access token — a read-only token can inspect functions, frontends, deployments and logs, and a full-scope one can also change configuration.

How do I keep the skills up to date?

Re-run volcano setup. It refreshes the source and reports each agent as installed, updated or already current, showing the version delta for marketplace plugins and the number of changed files for the rest. Claude Code and Codex need a restart to pick the new version up.

Ready to build with your agent?

Build, deploy, and scale on Volcano's global platform — free to start, with no infrastructure to manage.

Start building free

Explore more solutions

File storage on demand← File storage on demandBuilding AI agentsBuilding AI agents →