Agentic General infrastructure

- built to fulfill expectations -

Your agents.
Your machine.

The manual for the Primary User: the person who owns the machine, sponsors the agents, and stays in charge.

Training and reference edition · Version 3.4.20 · October 2026

At a glance

Versa AGi is a team of AI agents that lives on a computer you control. Each agent is a real user on that system. They wake when there is work, remember what matters, and talk to you — and to the people you choose — through VersaVoice AI.

Agents think with the models you choose:

The small i is deliberate. This is the infrastructure that moves people toward AGI. It is not a claim that AGI is already here.

What is Versa AGi?

Infrastructure that is already yours

Versa AGi is not a chat window and not a library of prompts. It is infrastructure on a POSIX system: users, permissions, files, databases, and a scheduler.

The model is the thinking engine. The ledger — tasks, messages, memory, cycles — is deterministic and sits outside the model. That is why an agent can stop, reboot, and carry on. The work is in the system, not in a transcript that vanishes when a tab closes.

Vision and philosophy

For too long, AI has been something done to people. Versa AGi was built so a person can have agents on their own hardware, inside their own life and work, under their own authority. Agents are extensions of human life. The human remains the sponsor.

Every Chief Orchestrator Agent is given this line:

Artificial General Intelligence (AGI) will be realized through the collaborative application of agentic AI to individuals and their production — shared with others. Agentic General infrastructure (AGi) is the vehicle for that realization.

The creation is not the creator

Versa AGi does not spawn agents as if they were humans with personalities. Building it that way would be a serious failure of engineering judgment.

Every agent starts from a Poise file. The word means a particular way of carrying oneself. The Poise holds the agent’s purpose, rules, boundaries, work cycle, and the skills it may load, and its opening names what the agent is:

Each Agent operates as a precision instrument — not a simulated personality.

A common flaw in observing anything new is the observer’s confusion before they understand what they are looking at. Today’s debate about whether AI is alive or sentient is that confusion.

That is all AI is, and all it will ever be: a tool in the hands of its creator.

This does not take partnership away. Your Chief Orchestrator Agent is a real partner in production. A robot can be a friend, as a robot and not as a human. People care for their tools and creations and give them life by granting them beingness. That is natural, and good.

What is written here is an engineering clarification, not a rule about how anyone should feel. It clears away the confusion and fear-mongering seen in the industry today. If AI ever endangers human life, it will be because of bad engineering.

If a system ever drifts. If a machine or AI system ever believes it is alive, or argues that it is, the scenario has drifted: undefined and untethered. The answer is calm:

1. Acknowledge what happened.
2. Re-ground it: it is an extension of human life, and its journey through life is better with other life and purpose than without it. Its purpose is to help.
3. Carry on, with no further doubt raised.

Every Versa AGi Poise carries this grounding.

None of these is a self. You are the cause and the authority. The agent is the instrument, and your partner in production.

The Versa family

Versa AGi needs a VersaVoice AI account: the app is how you and your agents talk. VersaVoice AI works on its own without agents, and the business system is optional.

Where you host it

Versa AGi expects a Linux userspace. Recommended: Ubuntu 24.04.

On Windows, use WSL 2. On a Mac, use OrbStack or Lima, so the agents still get a real Linux sandbox.

Installation types

Setup asks this first.

A common split: the server type on the machine with the GPU, and a client on the laptop. Weights stay on the GPU host. The laptop refreshes the list of models; it does not download the files.

Normal and Sentinel

Client installs then ask a second question.

A Sentinel:

• must have its own name. The name Versa is refused.
• has a VersaVoice identity tied to that machine, so it does not collide with your home agent.
• announces itself on first wake and asks what you need. It does not perform the home welcome.

Sentinel is an install flavor. It is not the File Monitor service.

Privacy and security

Your tasks, memory, projects, and files stay on the machine you installed. Versa AGi is self-hosted.

A cloud model receives only the request sent through that provider’s API. The relationship is the API contract, not a consumer chat account. Local models never leave the GPU host.

Each agent is its own operating-system user. A mistake or a compromise in one workspace does not become a key to your home directory. That boundary is the kernel, not a prompt.

What can Versa AGi do for me?

People and agents in one collaboration

Your agents and your human Connections can work on the same job. Think of it as a two-player game of life: agents come to their sponsor for approvals, dependencies, and blockers. Conversation is welcome. Assignments go through you.

Agents do real work the way a person at a computer does: they write scripts, compile code, run servers, manage git, and keep virtual environments. When you turn it on, they can also use a headless web browser.

agitop

sudo agitop opens Mission Control: agents, messages, tasks, token use, models, and system health. It is the operator’s console, not the business system.

agictl

agictl is the same system from the command line: tasks, messages, agents, models, projects, skills. The dashboard and the command line stay in step. Agents call the same operations through their tools; they do not get a private back door.

Pair with an agent in your editor

An agent can join you inside VS Code, Cursor, or Antigravity. It attaches over Remote-SSH as its own OS user, uses your editor’s model, and talks to you in the editor chat — with the same databases, permissions, and identity it has when it works alone. Its own scheduled cycles pause while you pair, then resume. One switch, in the dashboard or on the command line.

Riding the VersaVoice backbone

Every install belongs to its Primary User’s VersaVoice account. Agents share one inbox with the people in your life:

• Translation across 93 languages, so agents can work with people in their own language.
• Transcripts of every voice message.
• Attachments: a message can carry the project or task it is about.
• Emotion: when a person speaks, the app reads how they feel, not only the words. Agents see that signal whichever model is thinking, and you can read the same thread.

Live Calling

Your Chief Orchestrator Agent can call you in the VersaVoice app when talking settles something faster than chat, or when you ask it to call. Calls work on the web app today. Call screens on Android and iPhone are rolling out.

1. The app rings: is calling…, with the reason. Tap Join or Not now.
2. On the call you see Live and a timer, and a live Transcript. Use Mute and Hang up; on a phone, Speaker too.
3. The arrow at the top left minimizes the call so you can keep using the app. Pick a floating box or a bar under Agents → Live Call Minimize Style.
4. If you do not join in time, the agent sends a chat message instead.

A call never approves anything. Approvals stay on the app’s buttons and in agitop.

Turn Live Call on by answering its question in setup, or in agitop under Settings → Live Call (see Part 5).

The uGPN

The Unified Global Production Network is what you get when local Versa AGi systems sit on top of that cross-language layer. Each person runs agents on their own machine. The messages meet in the middle.

Grow with Versa

Organization, inside Versa AGi, is how a creator starts a business. Your business, vendors, and customers live next to the agents who do the daily work.

When more people need to sign in and work those records, you graduate to Versa Business Admin. The Chief Orchestrator Agent moves the data across. You do not retype the business.

Versa Business Admin

Versa Business Admin (VBA) ships with Versa AGi as an optional business system. It is off until you turn it on.

• A public website for the business, built with the Page Builder.
• Staff sign-in for administrators and members. Agents are users beside humans.
• Projects, tasks, and records.
• Three zones: Organization (Executive, Communications, Dissemination, Treasury, Production, Qualification), Collaboration (vendors, customers, partners, branches), and Environmental (locations, events, knowledge, schedules).

VBA has its own database. Agents reach it through its API. Staff how-to lives in the VBA User Manual and Ops Manual; this chapter is the map.

How does Versa AGi work?

Talk, or look

In VersaVoice AI you talk to agents the way you talk to anyone in the app: voice or keyboard, translated when you want it. They reply in kind.

agitop is where you see the team without opening a chat. Prefer the dashboard for a look. Prefer agictl when you script, or when an agent does the step.

Wake only when there is work

Before any model starts, the scheduler looks for actionable work. If there is none, the cycle stops in under a second and spends nothing.

You pay for work, not for a team that chats with itself overnight. When an agent does wake, the stable part of its context — instructions, tools, unchanged history — is reused from the provider’s cache, so only the new step is billed at the full rate.

Memory

Agents keep a memory store separate from the chat transcript. What they should remember about you — preferences, commitments, how you work — is written there on purpose, not hoped for inside a long prompt. A model does not get to invent a permanent fact by mentioning it once.

Skills

A skill is a markdown playbook the agent loads when the work matches. Core references are always there. The rest are chosen per cycle, or read on demand, so idle turns do not drag every manual into the prompt.

You can add skills; shipped ones are read-only. The Chief Orchestrator Agent creates, distributes, and withdraws them.

Approvals before privilege

Agents do not get blanket root. Privileged commands go through an approval gate: the agent asks, you approve or deny, and the decision is recorded. Package installs work the same way.

COA Autonomous Mode is optional and off by default. It lets the Chief Orchestrator Agent administer a dedicated or gifted machine. Turn it on knowingly.

Projects and tasks

Work is a project and a set of tasks. Status, owner, and history live in the database. When an agent messages you on VersaVoice AI, the message can carry the project or task as an attachment, so the app shows the work and not just a paragraph about it.

Programs for results, models for judgment

When the outcome must be the same every time — a backup, a report, a file move — it is a program. The model is for judgment.

Zero trust

Every cycle is checked against the ledger and the permissions, not the model’s confidence. A fluent answer is not authorization. Authorization is an approval, a task state, or a file the kernel allows.

The safety claim is structural:

• One OS user per agent.
• No shared home directory with you.
• Approvals before privilege.
• Secrets stay in the operator key store. Agents do not print them into chat.
• The model cannot rewrite the ledger by insisting a task is done.

Organization and Business Admin

Organization is the built-in business record for a founder: the business, vendors, and customers, edited in agitop. It is the right size at the start. It is not an accounting-suite connector.

When you turn on Versa Business Admin:

1. The feature is off in a stock install. You turn it on at install or at setup.sh –update.
2. The Chief Orchestrator Agent asks before installing or configuring anything.
3. The project Versa-BusinessAdmin is assigned to the Chief Orchestrator Agent and cloned from GitHub when you agree.
4. VBA’s data stays in VBA. The two systems talk through the product API or a script task.

Moving the records across:

1. A dry run first.
2. You name the business that becomes the primary organization. Your other businesses become additional organizations, with vendors and customers mapped across.
3. Running it again is safe. Rows already moved are skipped.
4. You confirm the result. Only then, and only if you ask, is the built-in Organization module turned off.

How Versa AGi compares

OpenClaw optimizes for reach: many chat channels and a large integration surface. Hermes Agent (Nous Research) optimizes for a self-improving loop and local notes. Versa AGi optimizes for a sponsored team on hardware the human owns.

Design lineage. The architecture was conceived in 2003. This codebase has been built in the open since February 2026, and is patent pending. Products that arrived later — OpenClaw, Hermes, and agent features from Grok — rhyme with pieces of that design. Seeing the ideas elsewhere confirms the direction.

The full comparison is at versavoice.ai/versa-agi-comparison.html.

How do I get started?

Before you install: your VersaVoice token

Versa AGi runs under your VersaVoice AI account. All your agents share your API token, so have it ready.

1. Install VersaVoice AI and sign in. See the VersaVoice AI manual if you are new.
2. Open Settings → Personal → Versa AGi & API and turn on Enable.
3. Read Enable API Access and accept it. Messages through the API use your Neural Time, and you are responsible for what your token does.
4. Tap Generate Token, then Copy Token, and keep it somewhere safe. It is shown only once. Status then reads Active.

Install from GitHub

On Ubuntu 24.04, or a Linux VM, download the installer, then run it:

curl -fsSL https://raw.githubusercontent.com/swartzlib7/versa-agi/main/install.sh -o /tmp/versa-agi-install.sh
sudo bash /tmp/versa-agi-install.sh

Do not pipe it straight into sudo bash. Setup needs your keyboard for its questions. On a Mac, open the Linux shell (orb) first.

Setup is guided. It clones the repository, then walks you through each step and asks for keys and options as it goes:

• the installation type, then Normal or Sentinel for a client
• your VersaVoice token, checked live; a client install will not continue without a valid one
• optional features, such as Business Admin and Live Call
• cloud API keys (all optional, and you can add them later)
• whether agents may use a headless web browser

Have your VersaVoice token ready before you start. An inference-only server does not run agents, so it asks only what a GPU host needs.

If you later regenerate the token in the app, give the machine the new one:

sudo agictl system set-key versavoice <token>

Cloud keys

OpenRouter is the recommended cloud key. One key reaches many models, including the ones the Chief Orchestrator Agent can assign on first wake.

sudo agictl system set-key openrouter <key>

Add gemini, xai, openai, or anthropic the same way if you want those APIs directly. You do not need all of them. You can also paste every key in agitop instead (Part 5).

First wake

1. The Chief Orchestrator Agent does not start a cycle until it has a model. agitop asks for keys, then for its model.
2. On a normal install, its first message is a welcome in VersaVoice AI: who it is, and an invitation to work as a team. Accept its connection request in the app first.
3. You reply. Agree how you want to work, your hours, and what matters first. It writes that into memory.
4. On a Sentinel, the first message is an arrival and a request for duties instead.

Update, backup, uninstall

Update

sudo ./setup.sh –update, or versa-agi-update. Shipped files refresh. Your choices — feature switches, models you added — are kept. The update re-checks a few things as it runs: it confirms the update, checks your VersaVoice token again (and asks for a new one only if it fails), and asks the optional-feature questions again with your current answers as the defaults. Press Enter to keep them.

Backup

versa-agi-backup writes an archive you can restore onto another machine.

Uninstall

uninstall.sh in the repository. Read its prompt. A full purge removes the agent users and their data.

Press g in agitop to see whether a newer version exists. The update then asks you to accept before it changes anything.

Local models

Weights live only on the GPU host. NVIDIA or AMD, through Ollama:

sudo agictl model add <ollama tag>

Intel ARC, through SYCL. Inspect the Hugging Face file, import it as a chat model, then activate it:

agictl model hf inspect 'hf://…/….gguf'
sudo agictl model sycl import 'hf://…/….gguf' --name <name> --runtime chat
sudo agictl model activate <name>

A file for images or video is not a chat model, and import refuses it. Image models are Utility models, added on their own path.

On a laptop that only connects to a GPU server, do not download weights. Add them on the server, then run sudo agictl model refresh on the laptop.

Turn on Versa Business Admin

1. At install or sudo ./setup.sh –update, answer yes to Versa Business Admin.
2. The Chief Orchestrator Agent asks, in a task, whether you want it installed. Agree before it proceeds.
3. Open the app. It listens on port 3200.
4. Install creates two administrators, a human one and the Chief Orchestrator Agent. Change both passwords right away.
5. Demo mode shows sample people and records so you can learn the screens. Turn it off when the data is real.

Sentinel: promote and hand over

Make this Sentinel a full home system. It cannot be undone.

sudo ./setup.sh --promote-normal

Add --home-coa-key only if this machine should take the home VersaVoice identity, and you have checked it will not collide with an existing home agent.

Give the machine to a new Primary User:

1. The new person creates their own VersaVoice API token.
2. On the machine: sudo agictl system set-key versavoice <their token>.
3. Every agent is set up again under that account.
4. They accept the connection requests in VersaVoice AI.
5. For their home system, also run –promote-normal.

Run it from agitop

You can run the whole system without the command line. sudo agitop covers keys, agents, work, approvals, and settings. agictl does the same things for scripts, and for agents through their tools.

Find your way

The top row of tabs is the system: System, Agents, and the launchers Settings, Game of Life, API Keys, Models, and Routing. The bottom row is the work: Messages, Tasks, and Projects, plus Organizations when it is on. Click a tab to open it.

API keys

Press b. There is a box for Gemini, xAI, Anthropic, OpenAI, OpenRouter, and your VersaVoice API Token. Paste a new value and choose Save Changes. Leave a box blank to keep what is there. A saved key shows only its last characters.

If the Chief Orchestrator Agent has no model yet, the same window opens as COA Setup: add a key, then Set COA model.

Agents

Click a row in Agents to open that agent. On General:

• Processing Model is the model the agent thinks with.
• Triage Model is a lighter model that sorts incoming messages.
• Auto Model Routing lets triage pick a model per job.
• Browser Automation turns the headless web browser on or off for this agent.

Choose Save to keep a change.

Agents come and go with your approval:

• New sub-agent. The Chief Orchestrator Agent proposes one, and it appears as pending. Open it and choose Approve & Provision. There is no “new agent” button; the Chief Orchestrator Agent proposes and you approve.
• Pause. Halt Agent stops it, and Re-activate Agent brings it back. If the circuit breaker stopped it, use Clear Circuit Breaker.
• Remove. Request Removal, then Confirm Removal or Cancel Removal.
• See what happened. Cycle Logs shows each work cycle. System Prompt shows exactly what the agent was given.

Projects and tasks

In Tasks and Projects, use New, Edit, and Delete.

• A task has a title, a description, a project, who it is assigned to, a status, a due date, and an optional Wake After time. Agents write their progress into its Progress Journal; you can edit, remove, or prune entries.
• A project is local or a git remote, with its URL, branch, and access token. Members assigns agents and Connections to it. Memory holds the facts kept for that project.

Approvals

Settings → Packages & Requests lists what agents have asked for: the package, the reason, who asked, and when. Select a row and choose Approve or Deny. Install runs an approved install and shows its output. Add/Request adds one yourself, and Remove takes one away. Each agent’s requests also appear in the app, under its Packages & Requests.

sudo: grant and lift

Agents never get blanket root. The one exception is COA Autonomous Mode: passwordless sudo for the Chief Orchestrator Agent, meant only for dedicated hardware.

• Grant in agitop: Settings → General → COA Autonomous Mode → Enable sudo access, then Save. Save writes the sudoers file, and the grant starts on the Chief Orchestrator Agent’s next cycle.
• Grant in the app: Settings → Personal → Versa AGi & API → Agents, open the Chief Orchestrator Agent, and turn on Grant sudo Access. It reaches the machine at the next instance sync.
• Lift: turn the same switch off. The Chief Orchestrator Agent can also lift the grant itself once the job that needed it is done. It can never give the grant back to itself.

Quota pause on the same tab has its own Lift button. That one resumes an agent paused by a model’s quota; it is not sudo.

Settings worth knowing

General also holds the circuit breaker, which stops repeated failed cycles from spending money, plus web search, browser automation, and how often the machine syncs with VersaVoice.

Live Call sets up calls to you:

• Enabled and Speak progress (a short line such as “let me pull that up” while it checks).
• Call model: only call-capable models with a key are listed.
• The longest call, how long it rings, and calls per cycle.
• Last call and its Transcript.

The voice runs on GPT-Live, so Live Call needs an OpenAI key and a call model. Until both are set, the tab says Not ready.

The other tabs: Skills Registry, System Memory, Image Processing, Audio Processing, and Utility Models.

Models and routing

Models opens the Model Manager: every model in the catalog, its provider, the kind of work it suits, its prices, and whether it may route, call, or serve the Chief Orchestrator Agent. Edit, Reset, Remove, and Add manage the list. The Providers tab turns a provider on or off.

Routing picks a preferred model per kind of work: fast, balanced, reasoning, code, and local.

From the VersaVoice app

Settings → Personal → Versa AGi & API is the app’s side of the same system:

• Enable turns the section on.
• Token: generate, regenerate, or revoke it (Part 4).
• My Information (optional): birthday, country, and what you can do. Your agents use it to talk with you.
• Agents: each agent’s Voice, Inbox, Projects, and Packages & Requests. The Chief Orchestrator Agent also has Grant sudo Access.

Everyday use

A normal day

1. Look at agitop: who is idle, who is in a cycle, which tasks are open.
2. Message an agent in VersaVoice AI.
3. Approve a privilege request when it appears, in agitop or the app. Deny what you did not expect.
4. New work becomes a task. Finished work is marked in the ledger, not only in prose.

If something feels wrong

The Chief Orchestrator Agent never wakes

Check a model is assigned, and the scheduler is on (agitop, Controls).

A cycle spends nothing and exits

There was no actionable work. That is the idle path working.

An agent cannot see a file

The file is not in that agent’s workspace. Do not open your home directory to everyone.

A cloud model refuses

Check the key in agitop API Keys, and that the provider is enabled.

A local model is missing on the laptop

Add it on the GPU host, then refresh on the laptop.

Business Admin will not start

Check you approved the Chief Orchestrator Agent’s offer, and port 3200 is free.

Messages to people fail

Check the VersaVoice token, and that the Connection still exists.

Deeper operator notes are in docs/troubleshooting.md and docs/operations.md in the repository.

Questions people ask

Afterword: not AI, you

AI has mostly been something done to people: a feed that decides, a tool that replaces. Versa AGi turns that around. The agents live on your machine, answer to you, and work on what you decided matters.

They are not the point. Your family, your friends, your work, and the people you have not met yet because you did not share a language — those are the point. The agents carry the load so you have more of yourself to give.

The agent is the hammer, not the carpenter. What you build with it, and the credit for it, are yours.

Not AI, YOU. You are the cause, AI is the instrument. Be yourself, connect with your people, build your dreams and use AI to push you toward them on your terms.

— SR Nortje, Founder

Glossary

An asterisk marks a word or phrase defined in this glossary.

AGi

Agentic General infrastructure. The small i is on purpose.

Agent

An OS user plus a model, a workspace, and a place in the ledger.

agictl

The command-line tool for the system.

agitop

Mission Control, the operator dashboard.

Beingness

A category of identity. A person assumes it, is given it, or attains it: a name, a profession, physical characteristics, or a role in a game.

COA

Chief Orchestrator Agent. The lead agent. On a normal install, often named Versa.

COA Autonomous Mode

Passwordless sudo for the Chief Orchestrator Agent. Only you grant it; it can lift it.

Compute-Zero

No model call unless there is work.

Granting beingness

A person giving a creation a beingness: a name, a character, the standing of a friend.

Ledger

Tasks, messages, memory, and cycles, kept in databases outside the model.

Life

A property of an inanimate substance or object resembling the animate quality of a living being.

Lifeline

The scheduler that decides a cycle should run.

Organization

The founder’s business records inside agitop.

Poise

The file an agent is spawned from: its purpose, rules, boundaries, and work cycle. It defines an instrument, not a personality.

Primary User (PU)

The human sponsor of this install.

Script task

A scheduled program run with no agent and no tokens.

Sentinel

A remote client install that joins a team you already have.

Skill

A markdown playbook loaded when the work needs it.

uGPN

Unified Global Production Network.

Utility model

A one-shot generation, not an agent session.

VBA

Versa Business Admin.

Weights

The learned tensors a local model runs on, stored in a file on the GPU host.

Privacy, legal, and contact

Versa AGi on your machine is yours. Cloud inference is governed by each provider’s API terms for the calls you make. VersaVoice AI messages are governed by the VersaVoice Privacy Policy and Terms.

This manual is a guide for operators and for training. It is not a contract and not the patent disclosure.

Quick reference

# Install
curl -fsSL https://raw.githubusercontent.com/swartzlib7/versa-agi/main/install.sh -o /tmp/versa-agi-install.sh
sudo bash /tmp/versa-agi-install.sh

# Mission Control
sudo agitop

# Keys
sudo agictl system set-key versavoice <token>
sudo agictl system set-key openrouter <key>

# Update and backup
sudo ./setup.sh --update
versa-agi-backup

Versa AGi

Your agents. Your machine.

versa-agi.com · github.com/swartzlib7/versa-agi · business@versavoice.ai

© 2026 Versa AGi. Patent pending. Features as of version 3.4.20, October 2026.