Official descriptionOpen source7d ago
vatio-ai/cli
Deploy and manage Vatio AI agents from your terminal. Node 20+, npx @vatio-ai/cli init
View on GitHub ↗Direct link · no redirect page
- Star count
- 0 ★ · vatio-ai/cli · read from the repository page · (checked 2026-10-16 20:00:20)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-10 · last seen 2026-10-10 · seen 1× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
- Install
npx @vatio-ai/cli
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx @vatio-ai/cli. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
vatio-ai/cli；first catalogued 2026-10-10；last seen 2026-10-10。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
@vatio-ai/cli
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
The CLI for Vatio, which gives the app you're building with
a coding agent — Claude Code, Cursor or Codex — an AI agent that knows the app
and its users. Your coding agent writes the agent into your project and drives
this CLI; Vatio runs the conversations, with your users signed in, an inbox for
your team, handoff to a person, and the replies your team reports turned into
tests.
Start here
In your app's project:
Then, in Claude Code, run /vatio-init (in Cursor or Codex, ask it to use
vatio-init). It reads your app, asks only what the code can't answer, and
pushes a preview for you to try. Then /vatio-add-to-app puts the agent in
your web, iOS, Android or Flutter app. See the docs.
By hand
No runtime to install first: if you have Node 20 or newer, you have this.
The package is @vatio-ai/cli; the command it installs is vatio. So
npm install -g @vatio-ai/cli gives you vatio push, and npx @vatio-ai/cli push
is the same thing without installing anything.
If you are a coding agent
vatio docs prints the same contract that
vatio.ai/docs/docs.md serves, and
vatio docs --save writes it next to the workspace.
Don't guess vatio.yml keys. Unknown root keys fail validation, and the rules
that judge a workspace live on the server — so the printed contract is the
current one by construction.
What a workspace is
A directory with a vatio.yml in it:
Only create the files you need. Nothing constrains where that directory lives —
an agent can sit inside the repository of the backend it calls, and every
command except init finds it by walking up from the current directory. There
is no --workspace flag.
Commands
--env NAME targets an environment: preview, the next version, or live,
what visitors talk to.
Run npx @vatio-ai/cli help for the whole surface, and see
vatio.ai/docs for the platform.
Where your credentials live
~/.vatio/config.json, or $VATIO_HOME/config.json — per developer, never
inside a repository. VATIO_BASE_URL and VATIO_TOKEN override it for one
command, which is what CI should use.
Where the rules live
Whether a workspace is valid is answered by Vatio, not by this package: push
and diff send the directory and read the result back. So the rules that
a coding agent — Claude Code, Cursor or Codex — an AI agent that knows the app
and its users. Your coding agent writes the agent into your project and drives
this CLI; Vatio runs the conversations, with your users signed in, an inbox for
your team, handoff to a person, and the replies your team reports turned into
tests.
Start here
In your app's project:
Then, in Claude Code, run /vatio-init (in Cursor or Codex, ask it to use
vatio-init). It reads your app, asks only what the code can't answer, and
pushes a preview for you to try. Then /vatio-add-to-app puts the agent in
your web, iOS, Android or Flutter app. See the docs.
By hand
No runtime to install first: if you have Node 20 or newer, you have this.
The package is @vatio-ai/cli; the command it installs is vatio. So
npm install -g @vatio-ai/cli gives you vatio push, and npx @vatio-ai/cli push
is the same thing without installing anything.
If you are a coding agent
vatio docs prints the same contract that
vatio.ai/docs/docs.md serves, and
vatio docs --save writes it next to the workspace.
Don't guess vatio.yml keys. Unknown root keys fail validation, and the rules
that judge a workspace live on the server — so the printed contract is the
current one by construction.
What a workspace is
A directory with a vatio.yml in it:
Only create the files you need. Nothing constrains where that directory lives —
an agent can sit inside the repository of the backend it calls, and every
command except init finds it by walking up from the current directory. There
is no --workspace flag.
Commands
--env NAME targets an environment: preview, the next version, or live,
what visitors talk to.
Run npx @vatio-ai/cli help for the whole surface, and see
vatio.ai/docs for the platform.
Where your credentials live
~/.vatio/config.json, or $VATIO_HOME/config.json — per developer, never
inside a repository. VATIO_BASE_URL and VATIO_TOKEN override it for one
command, which is what CI should use.
Where the rules live
Whether a workspace is valid is answered by Vatio, not by this package: push
and diff send the directory and read the result back. So the rules that
- Source
- github · https://github.com/vatio-ai/cli
- Browse by field
- Open source
- added
- 7d ago
More in Open source
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.