Quickstart

bashCopy
npm install -g veefore

One CLI for every project. Check it with veefore --version.

bashCopy
cd your-agent-project
veefore

The CLI connects to Veefore by itself. Every other address it needs, such as the gateway, comes from Veefore rather than from you.

From here veefore walks you through the rest. Each part is below.

The CLI opens the console. Sign in there (or create an organization), with SSO and MFA if your organization uses them, and approve the terminal after checking that the code on the page matches the one in your terminal.

textCopy
Sign in to Veefore https://veefore.example.com
  Opened your browser to finish signing in.
  Confirm the browser shows this code: KX7P-4MRT
✓ Signed in as dev@company.com in Acme (DEVELOPER)

The terminal never handles your password. Over SSH, veefore login --device prints a link and a code to enter in any browser instead. In CI, use VEEFORE_EMAIL and VEEFORE_PASSWORD. See Authentication.

The project is scanned on your machine. Nothing is uploaded, .env files are never opened, and credentials are reported by name only.

textCopy
✓ Framework: Vercel AI SDK (typescript)
✓ Found 2 tools:
    lookup_order             LOW     src/agent.ts:6
      calls orders.acme.internal
    refund_customer          HIGH    src/agent.ts:14
      calls api.stripe.com
! Your code reads 1 credential: STRIPE_SECRET_KEY (names only; values were not read)

Veefore will set up
  • Agent support-agent in Development
  • 2 tools, each with its own capability, authorized for this agent only
  • A starter policy, in OBSERVE mode: decisions are recorded, nothing is blocked yet
Set this up? [y/N]

Answer once. Veefore creates the agent with a key pair generated on your machine (only the public key is sent), registers each tool with its own capability, authorizes it for this agent alone, and adds the starter policy.

It writes veefore.config.json (no secrets, commit it) and .env.local (the private key, mode 0600, gitignored). Veefore cannot recover the private key; move it into your secret manager before deploying.

Each tool's function is wrapped in guard(), so Veefore decides every call before your code runs. You see the diff first:

diffCopy
+import { guard } from '@veefore/sdk';
 ...
-    execute: async ({ amount }) => {
+    execute: guard('refund_customer', async ({ amount }) => {
       return stripe.refunds.create({ amount });
-    },
+    }),

Your function bodies are not edited. Files are backed up, your own typecheck runs afterwards, and if it newly fails every file is put back automatically. veefore undo reverses the change at any time.

Tools the rewrite will not change on its own are yours to choose: exact instructions to do it by hand, AI with your own model key, or Veefore AI. See Automatic setup.

Then install the SDK the change imports:

bashCopy
npm install @veefore/sdk

bashCopy
pip install veefore-py

bashCopy
veefore dev

Run your agent as you normally do, from the project directory. Every protected call streams in with the decision, the rule that produced it, and the next step.

New environments start in OBSERVE, so calls execute and Veefore records what enforcement would have decided:

jsonCopy
{
  "decision": "ALLOW",
  "outcome": "OBSERVED",
  "mode": "OBSERVE",
  "shadow": { "decision": "REQUIRE_APPROVAL", "reason": "Tool is flagged dangerous." }
}

bashCopy
veefore policies test
veefore deploy --mode ENFORCE --reason "Refund policy reviewed and approved"

Preflight replays your recent observed traffic and shows exactly which calls start being refused before anything changes, then asks for confirmation, a reason and step-up. Under ENFORCE, a refused tool throws in your agent and its body never runs.