Nexotao Agent

Nexotao Agent is a self-hosted control plane for coordinating AI-agent teams through the Nexotao model ecosystem.

It combines company and project management, agent configuration, task ownership, execution history, budgets, approvals, secrets, and operational visibility in one web application. Nexotao is the recommended adapter, while the existing process, HTTP, Claude Code, Codex, Gemini, OpenCode, Cursor, Hermes, Pi, and OpenClaw adapters remain available for compatibility.

This repository intentionally contains no promotional screenshots, banners, or videos. The product and its behavior are documented in text so the documentation stays reviewable and current.

What is different

• Nexotao-first routing. The recommended adapter sends supported models through https://api.nexotao.com.
• Protected credentials. NEXOTAO_API_KEY is stored as a company secret and bound to agents instead of being saved in plain configuration.
• Provider isolation. Claude runs ignore inherited Foundry, Vertex, Bedrock, and legacy Anthropic API-key settings that could redirect traffic away from Nexotao.
• Explicit task state. Nexotao runs do not infer a blocker or planning-only result from ordinary prose. Those states require structured output.
• No recursive status workers. A successful Nexotao run does not create another worker merely because its source task remains open.
• Conservative recovery. Legacy heuristic recovery automation is disabled by default. Operators can still inspect, retry, reassign, pause, or resolve work explicitly.
• Nexotao identity. The web UI, onboarding, startup banner, service deployment, and default product copy use Nexotao Agent.

Nexotao models

The adapter discovers models from the Nexotao catalog and falls back to this built-in list when discovery is unavailable:

| Model | Recommended | Execution lane | | --- | --- | --- | | claude-opus-4-8 | Yes | Claude Code | | claude-opus-4-7 | Yes | Claude Code | | claude-opus-4-6 | Yes | Claude Code | | claude-sonnet-4-6 | No | Claude Code | | gpt-5.6-terra | Yes | OpenCode compatibility mode | | gpt-5.6-sol | Yes | OpenCode compatibility mode | | gpt-5.6-luna | No | OpenCode compatibility mode | | gpt-5-mini | No | OpenCode | | DeepSeek-V4-Pro | No | OpenCode | | DeepSeek-V4-Flash | No | OpenCode | | grok-4.3 | No | OpenCode |

The GPT-5.6 Luna, Sol, and Terra chat endpoints currently reject tool definitions. Nexotao Agent therefore treats them as text/reasoning models for planning, review, and advisory roles. Use a recommended Claude Opus model for autonomous file, shell, and API work.

Core capabilities

• Multiple isolated companies in one instance
• Goals, projects, tasks, dependencies, comments, and documents
• Agent org charts, reporting lines, roles, permissions, and budgets
• Nexotao and compatibility adapters
• Persistent sessions, run logs, usage, cost, and audit history
• Approval gates and human operator controls
• Project and execution workspaces
• Secret bindings and scoped tool access
• Schedules, routines, pipelines, plugins, and company export/import
• Authenticated or trusted-local deployment modes
• Embedded PostgreSQL for local use and external PostgreSQL support

Requirements

• Node.js 20 or newer
• pnpm 9.15.4
• Git
• A Nexotao API key for the Nexotao adapter
• Claude Code for Claude models, or OpenCode for GPT, DeepSeek, and Grok models

Quickstart

Install the CLI globally and start Nexotao Agent:

npm install --global nexotao-agent
nexotao

The first launch opens the interactive setup flow, validates the local environment, and starts the web application. The legacy paperclipai executable remains available as a compatibility alias.

To run from source instead:

git clone https://github.com/rizkyriyadi/nexotao-agent.git
cd nexotao-agent
corepack enable
pnpm install --frozen-lockfile
pnpm dev

Open http://localhost:3100. An embedded PostgreSQL database is created automatically.

For a production build:

pnpm build

The server entry point is server/dist/index.js; the built UI is in ui/dist.

Configure the Nexotao adapter

1. Create or claim an instance.
2. Create a company.
3. Store an sk-nexo-... key as a company secret.
4. Create an agent and choose the Nexotao adapter.
5. Bind the secret as NEXOTAO_API_KEY.
6. Select a model and run the environment test.
7. Assign a task or trigger the agent manually.

The gateway URL is enforced by the adapter and cannot be overridden from an agent configuration.

Task execution model

A task has one assignee and uses atomic checkout when execution begins. Runs record their session, logs, status, usage, result, and task context. Nexotao agents must report important orchestration states explicitly:

• blocked when external input is genuinely required
• plan_only when the run intentionally produced only a plan
• a normal successful result when useful work advanced

Ordinary phrases such as “next steps” or “waiting” do not automatically mutate task state. Empty responses and unresolved work remain visible for operator action without spawning recursive recovery runs.

Documentation

• Product definition
• Technical specification
• Nexotao adapter
• Task orchestration
• Deployment
• Development
• Design principles
• Roadmap
• Security policy

Verification

pnpm typecheck
pnpm test
pnpm build

pnpm test runs the Vitest suite. Browser tests remain separate under pnpm test:e2e.

License

MIT. See LICENSE.