Get started with SingleIntent

Put your existing AI subscriptions to work as a team

SingleIntent is a Node.js application with a local web app for building and coordinating an AI organization. Create agents, give them roles and reporting lines, coordinate work, and follow activity. OpenClaw connects the organization to the model providers, tools, and messaging channels you configure.

For most common setups, Welcome & setup guides you through connecting the OpenClaw engine, installing and connecting the SingleIntent plugin, checking whether a configured model route can answer, and trying a first message with the main agent. Teams and messaging channels are optional and configured separately.

Install and start the app

SingleIntent requires Node.js 24.16.0 or later in the 24.x line, or 26.1.0 or later. Node 25.x is not supported.

Supported range: >=24.16.0 <25 || >=26.1.0

Check your Node.js version:

node --version

Install the app and start it from your terminal:

npm install -g https://singleintent.com/releases/latest.tgz
singleintent init

The first command installs the app; the second starts its local web server and opens it at http://127.0.0.1:5173. Keep the terminal open while using the app. Press Ctrl+C there to stop the server. The download is public; no account or token is needed to get it.

Welcome & setup

In the app, choose Welcome & setup. The checks run against the current setup each time; a passing check is evidence about that check, not a guarantee that every team workflow or optional integration is ready.

1. Connect the OpenClaw engine. The wizard checks whether the engine is available. If it needs to install a product-managed engine, it explains the change and asks first; if that engine is installed but stopped, it offers to start it. It will not silently replace a background service it cannot verify.
2. Install and connect the SingleIntent plugin. The plugin links OpenClaw to this SingleIntent instance. The wizard checks whether it is installed and connected to the right instance.
3. Check model access. The app asks an agent for a real reply, which uses a model call. If no configured route answers, the app explains the next setup step. Provider sign-in may need to be completed interactively outside the app; the app cannot observe that terminal step, so return and check again. Supported sign-in methods and billing depend on the provider and OpenClaw configuration. A consumer chat subscription does not automatically include API access.
4. Try a first agent message. The first-agent step asks main to handle a request and shows its reply. That confirms one model-backed response—not that every agent, tool, project permission, or channel is ready for your intended work.

If the wizard reports an existing or unrecognized OpenClaw background service, do not install or start another service beside it. Follow the recovery instruction shown in the app.

Build and coordinate your organization

Create a project, add agents, assign roles and reporting lines, and track work and activity. Agents can coordinate directly; you can step in when a decision needs you. A project association does not itself grant access to files, repositories, or tools—those capabilities depend on your OpenClaw configuration.

Learn lets you ask an agent to update durable instructions from a session. The app verifies the expected workspace files changed; inspect the result. This is user-directed, not autonomous self-improvement.

Use the model access you have

SingleIntent works with model routes configured through OpenClaw. Where supported by your provider and setup, an existing authenticated subscription sign-in may be usable; otherwise, OpenClaw can be configured with API credentials or another supported provider route. The provider receives the model request and applies its own access and billing terms. Check the provider and OpenClaw guidance for your specific sign-in method.

SingleIntent runs as a local Node.js app and keeps its product/project work state on your computer (in ~/.si by default). Model inference goes through the provider configured for the selected route; the exact execution location depends on that provider. Local tools can act on resources available to OpenClaw on this machine. External tools and messaging channels send relevant requests or messages to the services that handle them. This is not a security sandbox.

Connect messaging channels (optional)

Bring agents into channels supported by your OpenClaw version and installed integrations—for example, Slack, Telegram, WhatsApp, Discord, Microsoft Teams, Signal, Matrix, or LINE. Each channel requires its own account setup, authentication or pairing, access controls, and agent routing. Channel messages go through the service configured for that channel. See the OpenClaw channel guide.

Verify a real task

Give the team a small, low-risk task that exercises the model and any tool access you intend to use. Review the agent activity and available output. A model check proves that one route answered; a real task helps you confirm the organization and configured connections work for your use case. Expand access only as needed.

If setup pauses

• Node.js version rejected: install a version in the supported range, then start SingleIntent again.
• Engine or plugin check fails: follow the step-specific message. Do not reinstall over an existing service you do not recognize.
• No model can reply: follow the provider setup instruction, complete any interactive sign-in, then return to Welcome & setup and check again. The check makes a real model call and may use provider quota or incur usage.
• Port 5173 is busy: use the supported port option when starting the app.
• Dependency install warning: if your package manager reports an install-script warning, check whether the install completed before retrying; avoid installing the app twice.