Product · Vagaris

Governed AI execution in a CLI, with the admin surface beside it.

Vagaris is the customer command surface for running AI work locally, remotely, or in hybrid mode, and the operator surface for approvals, companies, agents, and heartbeats. This page only states what the current CLI tree, docs, and phase ledger prove today.

Canonical command: vagaris · compatibility alias: vagris (deprecated, warns on stderr)

Read the current CLI docs Pricing Platform & admin

Overview

What is shipped now.

First run

The onboarding flow detects local capabilities and the repository, resolves sign-in, resolves organization and role, and chooses local, remote, or hybrid execution without manual config editing on the normal path.

Execution surfaces

Local adapters for Codex, Claude, and Gemini ship beside process and HTTP executors. Node enrolment and node health commands are part of the public CLI surface.

Control plane

Issue, company, agent, approval, activity, dashboard, and heartbeat command groups are documented and wired. The browser console remains an internal surface.

Install

Available now, and what is still pending.

Public npm and Homebrew installation are live. Each command below was run on a clean prefix and a clean Homebrew cellar before this page claimed it.
npm install -g @vagarylabs/vagaris
vagaris --version

Or with Homebrew:

brew tap Cramraika/vagaris
brew install vagaris

Or without installing anything:

npx --yes --package=@vagarylabs/vagaris vagaris --version

The package is @vagarylabs/vagaris; it links two commands, vagaris and the legacy alias vagris. Node 20+ is required. A cloned checkout still works for development: pnpm install then pnpm vagaris onboard --yes.

Docs

CLI documentation is summarized here, with the source truth named.

CLI-specific source docs still ship with the repository; this site now hosts the current public summary at /docs/vagaris.

Quickstart

Repository-local onboarding and run flow. This is the demonstrable install path today.

CLI overview

Global flags, context profiles, secrets commands, and the current command map.

Setup commands

onboard, run, doctor, configure, env, and private-hostname allowlisting.

Control-plane commands

issues, companies, agents, approvals, activity, dashboard, and heartbeat.

Deployment overview

local_trusted, authenticated/private, and authenticated/public deployment modes.

Supported platforms

Node 20+ target, supported OS matrix, and the intended installer surfaces.

Developers

Use your local coding tools, not a separate runtime stack.

Local coding-agent adapters

Codex Local, Claude Local, and Gemini Local are documented adapter surfaces, each with environment checks and local CLI wiring.

Codex Local · Claude Local · Gemini Local

Developer workflow

The repository quickstart runs on Node 20+ with embedded PostgreSQL by default. Manual local agent shells can be provisioned from the CLI, for example vagaris agent local-cli codexcoder.

Node enrolment

vagaris node enroll, status, doctor, and capabilities are part of the node surface, with machine fingerprinting and operator approval on enrolment.

Hybrid execution

The onboarding shell auto-selects local, remote, or hybrid mode from observed capabilities. Docker presence promotes the default to hybrid mode rather than asking users to hand-edit runtime config.

Platform & Admin

The CLI already carries the operator work.

Issues

List, create, update, comment, check out, and release work from the command line.

Companies

List companies, inspect them, and import or export company state for controlled transfer.

Approvals

Review, decide, resubmit, and comment on approvals without dropping to raw API calls.

Agents & skills

Inspect agents, browse the shipped skills catalog, install skills into a company, and sync them onto agents.

Activity & dashboard

Read recent activity and pull dashboard state from the same CLI that runs the system.

Internal browser console

The four-lens fleet console is live for operators, but remains an internal surface. Public readers get the plan and topology, not a fake self-serve console promise.

Departments

Department-aware authority is real, and its current depth is named.

This page intentionally does not claim broader department projections or commercial packaging beyond what the current contracts and routes expose.

16 catalogued departments

The shared department catalog now carries sixteen rows, including research and strategy, and the public contract consumes that catalog rather than restating its own count.

Three grant tiers

The current department ladder is watch → operate → own. Grantable tiers and effective proof clamps are part of the shared contract.

Current projection depth

Today's proven surfaces are company grants, seat-to-department resolution, per-department metrics, and capability mapping. This page does not advertise deeper projections than that.

Security

Authority and evidence are part of the product, not afterthoughts.

Browser or device sign-in

The CLI uses the fleet identity authority for authorization-code + PKCE login, with the native client callback fixed at /oauth2/callback/vagaris.

Governed acts

The shared governed lease contract answers all twelve act axes: tier, scope, tool posture, armed state, entitlement, department grant, budget, run ceiling, freeze state, approval, and host act-key.

Secrets and support bundles

Secrets doctoring and migration commands ship in the CLI, and support bundles are regression-tested against planted secrets so evidence export does not leak tokens or keys.

Private networking

Authenticated private deployment and hostname allowlisting are documented for tailnet and LAN use. Public deployment exists as a documented mode, not a hand-waved future adjective.

Enterprise

Private deployment is real; enterprise packaging is still conservative.

Current deployment docs cover local_trusted, authenticated + private, and authenticated + public modes, plus Tailscale-friendly reachability and hostname allowlisting.

Node enrolment, operator-approved node registration, and private-network deployment are part of the code and docs today. Procurement-heavy white-label or private-cell claims are not advertised here because they are not yet a public shipped contract.

Pricing

Current public pricing is the organization plan surface.

The truthful public pricing contract today is the organization-plan page at /pricing. Paid activation is assisted today; self-serve card upgrade is not live yet.

Department breadth, executor costs, and model-provider commercial terms are deliberately not invented on this page. When a number or entitlement is not shipped as a public contract, this page says so instead of guessing.

Open pricing