VEKTRAHello.I’m OpenMango.
The terminal adapts to the problem. The model adapts to the terminal.
Apache-2.0 · curl install · the open operator layer for any agent backend.
Run om. It senses your workspace, provisions your Mangos Drive on AgentDrive, and launches any AI backend with full context.
Install
vektraindustries.com/openmango/install · Node 20+ · clones to ~/.openmangos/src
Update
Launch
live terminal
$ om sense
mode build · stack node,typescript
✓ Mangos Drive · workspace + personal swarms
$ om
OpenMango boot → opencode
recall → pack → heal → launch
OpenMango — the open bet
Not another fable you rent.
Premium agent surfaces keep closing behind tiers and APIs. OpenMango keeps the operator layer public — terminal, memory fabric, and orchestration on your machine, composable with whatever model you already trust.
Not the viral acronym
On X, MANGOS means the new FAANG — Meta, Anthropic, NVIDIA, Google, OpenAI, SpaceX. OpenMango is the opposite wager: the open operator layer underneath all of them.
MANGOS on X · TechCrunch →Closed agent product
OpenMango
One vendor's model + UI
Any backend — OpenCode, Grok, Claude, Codex, Cursor
Session memory in a walled garden
Mangos Drive on open AgentDrive — your namespace, your swarms
"Trust us" orchestration
om sense → explainable situation graph; you see what adapted and why
Install = account + subscription
curl | bash → source on disk, Apache-2.0, forkable
OpenMango
The canonical product name — one mango, open by default. npm package, paths, and env stay openmangos / OPENMANGOS_* for compatibility.
Many varieties, one tree
Backends, modes, problem types — an open ecosystem you compose. Not a single rented narrative behind glass.
Operator layer
Sense the real environment, pack honest context, route to the best tool, verify when work is done. Human commits always.
Hard hat, not demo glass
The mascot wears infrastructure gear because this is substrate work — terminal, memory fabric, orchestration on your machine.
What Mangos stands for
You already have the agents — Codex, Grok, Claude, OpenCode, Cursor. OpenMango is the operator shell that makes the terminal worthy of them: sense your real workspace, recall across sessions on AgentDrive, and launch any backend without lock-in.
Operator flow
01
Install
Node 20+, git, npm link. Source lands in ~/.openmangos/src.
curl -fsSL https://vektraindustries.com/openmango/install | bash
02
Onboard
Six-step wizard: prerequisites, workspace init, Mangos Drive, preferred backend.
om onboard
03
Run
Bare om bootstraps — sense, recall, pack, heal, launch your agent with full context.
om
Capabilities
One command install
curl from vektraindustries.com clones OpenMango, builds, links om globally, and runs the onboarding wizard.
Adaptive terminal substrate
om senses your workspace, picks mode and backend, packs context, and launches OpenCode, Grok, Claude, Codex, or Cursor.
Mangos Drive memory
User-scoped AgentDrive namespace — workspace swarm + personal swarm — provisioned on first om onboard.
Session learning loop
om wrap captures OpenCode transcripts, names child skills from session intent, and recalls them on the next boot.
Operator-first
Human commits always. Healing, doctor checks, and verify gates — no black-box verdicts.
🥭 Mangos Drive
Your named memory namespace on AgentDrive — workspace swarm and personal swarm — provisioned when you run OpenMango.
om drive status · om recall · om remember