Docs

SGT Fleet: install and use (for people and AI agents)

SGT Fleet gives Claude Code and Codex low-cost Flash agents on Ollama Cloud, installed with one line. Your Claude Code or Codex plans and checks; SGT agents write the deliverables.

Last updated 27 September 2026

Quick answers

Is SGT Fleet free for students and educators?

Yes — SGT Fleet itself is free for verified students and educators. The person, not the agent, selects Free at https://sgtfleet.com/onboarding/, enters their true school, role and email, ticks the declaration and submits. Some applications may be approved automatically: when the approval returns an inline one-use download link, that private link appears in the status line on the onboarding page. Anything unclear goes to a short human review, and the person is emailed when it is decided. If an application is approved without an inline link, the private one-use download link is delivered by email instead. No payment is collected and no Stripe checkout is involved. Free SGT access does not include free Ollama, OpenAI or Claude usage: the person still needs their own Ollama Cloud key or entitlement, and should check provider charges before any real Flash call.

How do I reduce Claude Code token usage with SGT Fleet?

Let Claude Code hand its deliverables, such as websites, three.js scenes, scripts and documents, to SGT Fleet's specialist agents, while Claude Code keeps planning, checking and judging. Install SGT Fleet with one line (irm https://sgtfleet.com/install.ps1 | iex), open a new Claude Code session in your project and ask for what you want built. Measured results and their limits: https://sgtfleet.com/benchmarks/

How much frontier-model usage does SGT Fleet reduce?

SGT's own internal measurement found 80% fewer frontier tokens when the frontier model is forced into orchestration mode and the work goes to Gap Closers. It is a first-party measurement, not an independent audit, and the raw counts and method are not yet public. Optional JEV is a separate result: in one repeatable Frontier-templated routine workflow it cut frontier-orchestration cost by 50% on the eligible remaining work — a cost measure, not a token count, and not a 50% cut to all tokens. The 90% sometimes quoted is conditional sequential arithmetic on top of the 80%, not a measured combined run, and no bill saving is promised. Detail and limits: https://sgtfleet.com/benchmarks/

How do I run Claude Code or Codex sub-agents on a cheaper model?

SGT Fleet's agents run on DeepSeek Flash (deepseek-v4.1-flash:cloud) through Ollama Cloud, using your own Ollama API key. The installer connects the SGT tools to Claude Code and Codex, and your frontier model calls them itself: sgt_run_agent sends one complete task, sgt_job follows it, and sgt_judge records the verdict after its own check. SGT Fleet is billed separately from your Claude, OpenAI and Ollama usage.

How do I use DeepSeek Flash with Codex?

Install SGT Fleet with the same one line. Setup connects the SGT tools to Codex (version 0.157 or later, signed in with codex login) and adds a short SGT block to %USERPROFILE%\.codex\AGENTS.md. Open a new Codex session in your project and ask for what you want built: Codex plans and checks, and SGT's Flash agents write the files. sgt codex starts the same session with an end-of-session check of which files the agents wrote.

Does SGT Fleet run on macOS or Linux?

Not yet. The current release runs on Windows 10 or 11 (x64) with Windows PowerShell 5.1.

How much does SGT Fleet cost?

Personal is $5/month, Enterprise is $10 per seat per month, and SGT Fleet is free for verified students and educators. Model usage is billed separately by your own providers. Plans: https://sgtfleet.com/onboarding/

Start here

• I am a student or educator: choose Free at https://sgtfleet.com/onboarding/ — the person selects Free, enters their true school, role and email, ticks the declaration and submits. An agent must not fill in this form or claim eligibility for you.
• I bought SGT Fleet: open PowerShell and run the one line below. Paste the personal download link from your purchase email when it asks.
• I have an SGT key: run the one line below and enter it at the installer's hidden prompt.
• I am new: choose a plan or register as a student.

Who does what

• The person: chooses the plan (free academic or paid), enters their own truthful details, keeps the private link and keys out of agent chat, signs in to Claude Code or Codex, and checks their Ollama Cloud entitlement and charges.
• The installer: everything else.
• Claude Code or Codex: sends each deliverable to an SGT agent with the SGT tools, checks the written files itself, and records the verdict.

1. What you need

• Windows 10 or 11, x64, with Windows PowerShell 5.1.
• Claude Code (npm i -g @anthropic-ai/claude-code, then run claude once and sign in) and/or Codex (npm i -g @openai/codex, version 0.157 or later, then codex login).
• An Ollama account and API key, with the entitlement and charges you expect. SGT Fleet is billed separately from your Claude, OpenAI and Ollama usage, and free SGT access does not include free Ollama, OpenAI or Claude usage.
• An SGT plan at https://sgtfleet.com/onboarding/:
• free for verified students and educators (no payment is collected);
• Personal $5/month;
• Enterprise $10/seat/month.

2. Get access (the person)

• Students and educators (free): select Free on https://sgtfleet.com/onboarding/, enter your true school, role and email, tick the declaration and submit. Some applications may be approved automatically: when the approval returns an inline one-use download link, that private link appears in the status line on the onboarding page. Anything unclear goes to a short human review, and you are emailed when it is decided. If an application is approved without an inline link, the private one-use download link is delivered by email instead. No payment is collected and no Stripe checkout is involved.
• Personal and Enterprise (paid): pay at Stripe-hosted Checkout; agents never enter card details. The confirmation page shows a Download button and the purchase email carries your personal download link. It works while the subscription is active.
• Then, the person: keep the private link and your keys out of agent chat, sign in to Claude Code or Codex yourself, and check your Ollama Cloud entitlement and charges before any real Flash call.

3. Install

The person must already hold the private download link (or an SGT key) and the Ollama key before this step; approval and provider entitlement come before installation, and the agent runs the installer.

The person stays at the computer for this step. When no key file is present, the installer asks for the private one-use link or SGT key, and its setup asks for the Ollama key, in hidden prompts (Read-Host -AsSecureString) — the characters are never echoed and never typed into an agent chat. Answer both prompts yourself; this is not an unattended install.

Then the agent (or you) runs the one line:

irm https://sgtfleet.com/install.ps1 | iex

It does 8 steps and prints each one:

1. checks Windows and PowerShell; 2. finds the release package; 3. gets access: it reads %USERPROFILE%\sgt-key.txt if present, otherwise it asks, in a hidden prompt, for the SGT key or the personal download link from the purchase email; 4. downloads the package (about 195 MB); 5. checks its SHA-256 before unpacking anything; 6. installs to %LOCALAPPDATA%\Programs\SGT-Fleet, keeps the previous version, and puts the sgt command on PATH; 7. runs setup: activates this PC; reads %USERPROFILE%\ollama-key.txt (or asks in a hidden prompt), tests it with a real Flash call and stores it encrypted for this Windows user; runs the one-time grounding check; runs one real agent job as a self-test; connects the SGT tools to Claude Code and Codex; adds a short SGT block to %USERPROFILE%\.claude\CLAUDE.md and %USERPROFILE%\.codex\AGENTS.md. It does not change Claude Code or Codex permissions; 8. runs sgt doctor and turns on automatic updates (a daily per-user Scheduled Task).

It ends with "SGT Fleet is READY." The first run takes several minutes because of the one-time check. Any failure stops with one FAILED line saying what to fix. Running the one line again repairs the install. It uses this PC's saved activation, so the key file is optional.

4. Use

• Open a new Claude Code or Codex session in your project and ask for what you want built. sgt claude and sgt codex start the same session with an added end-of-session check of which files the agents wrote.
• Claude Code or Codex uses the SGT tools itself (the setup block tells it how):
• sgt_status: activation and the Flash connection;
• sgt_agents: the agents and what each one owns;
• sgt_run_agent: sends one complete task to the agent that owns the craft; the agent writes the files;
• sgt_job: follows the job until it is done;
• sgt_gate_open and sgt_gate_pass: record the check of the written files;
• sgt_judge: records CORRECT or WRONG for the job (after WRONG, run again with a clearer task);
• sgt_cancel stops a job; sgt_knowledge returns an agent's guidance.
• The orchestration rule: your Claude Code or Codex plans, sends each deliverable to an SGT agent, checks the files itself and judges them; SGT agents write the deliverables.
• Agents:
• SGT-Weaver: websites;
• SGT-Vista: three.js scenes;
• SGT-Playwright: browser games;
• SGT-Scribe: files, scripts, documents;
• SGT-Forge: app scaffolds;
• SGT-Animus: animated figures;
• SGT-Sculptor: Blender assets;
• SGT-Droid: mobile screens;
• SGT-Infra: deploy units;
• SGT-Anvil: Blender add-ons.

5. Updates

• SGT Fleet keeps itself up to date: no new key, link or install command is needed.
• A daily Scheduled Task ("SGT Fleet Update", your Windows user only, no stored password) checks for updates. sgt claude, sgt codex and sgt doctor also check, at most once a day.
• An update installs only when no SGT, Claude Code or Codex session is using SGT. Otherwise it is downloaded, checked and applied at your next sgt claude, sgt codex or sgt doctor. You see SGT Fleet OLD → NEW installed (notes: …) or update NEW ready, will apply when sessions close.
• Every update is signed. SGT checks the release signature and the package SHA-256 before unpacking anything. After installing, it runs setup and sgt doctor; if either fails, it rolls back by itself and says so in one line. The last two good versions are kept.
• Commands: sgt update checks and installs now; sgt update --check shows the installed and the latest release; sgt update --rollback goes back one version; sgt update --disable-auto and sgt update --enable-auto turn automatic updates off and on; sgt update --channel preview gets early releases (--channel stable returns).
• Offline, the check is skipped and the installed release keeps working.
• When a subscription ends, updates stop and SGT Fleet stops at its next start. Your projects and settings stay. Renew at https://sgtfleet.com/account/ and everything resumes with the same key.
• Installs made before 27 September 2026 have no updater yet: run the one line once. It uses this PC's saved activation, so no key file is needed.
• Release notes: https://sgtfleet.com/releases/

6. Check and fix

• sgt doctor checks activation, the Ollama key with a real Flash call, grounding, the self-test, and Claude Code or Codex (sign-in, and Codex 0.157 or later). It prints a JSON report with "ok" and a fix for each failure; exit code 0 means healthy.
• sgt setup repeats setup; running the one line again does the same and also installs the latest release (updates normally install themselves: see 5. Updates).

7. Keys and seats

• Your key belongs to your subscription and does not change: downloading, updating or reinstalling never replaces it.
• A seat is one PC. To move, run sgt logout on the old PC (or choose Release seat at https://sgtfleet.com/account/), then install on the new PC with the same key.
• A seat unused for 30 days is freed automatically.
• A new key is issued only when you choose Issue new key at https://sgtfleet.com/account/ (you type REPLACE to confirm). That stops the old key everywhere.
• Your account page, https://sgtfleet.com/account/ (sign in with Google), shows your subscription, the current release, and each seat with its key and PC, with Release seat, Issue new key and Download latest.

8. Remove

Run sgt logout to free the seat, then sgt uninstall: it removes the Claude Code and Codex connections and the SGT blocks, and also removes the update task. Then delete %LOCALAPPDATA%\Programs\SGT-Fleet and %LOCALAPPDATA%\SGT-Fleet.

9. How it works

• The SGT tools reach Claude Code and Codex through a local connection that setup registers; your files stay in your project, and the SGT engine stays in %LOCALAPPDATA%. Do not copy the engine into projects.
• Grounding is automatic and runs in the background: when SGT's own knowledge sources change, they are re-checked while agents keep working on the last accepted review.

Plain-text version for agents: /llms.txt