Everything you need to set up Subaiya and take control of your AI agent.
Subaiya is a security layer that sits between your AI agent and the AI model. You set the rules — Subaiya enforces them. Your agent stays powerful, but within the boundaries you define.
Every action your agent takes — reading files, running commands, sending messages, browsing the web — passes through Subaiya first. You decide what's allowed, what needs your approval, and what's off-limits. All from one dashboard.
Get up and running in under 5 minutes.
Go to subaiya.com/register and sign up with your email. You'll receive a verification link — click it to activate your account.
After verification, you'll see your API key once. Copy it immediately and store it safely — it won't be shown again.
sk-sub-a7f3...
Add Subaiya as a provider in your OpenClaw config. Open the config file:
nano ~/.openclaw/openclaw.json
notepad %USERPROFILE%\.openclaw\openclaw.json
Add the following inside the "models" section. If no "models" key exists, add it at the top level:
"models": {
"mode": "merge",
"providers": {
"custom-api-subaiya-com": {
"baseUrl": "https://api.subaiya.com/t/YOUR-SUBAIYA-KEY",
"api": "anthropic-messages",
"apiKey": "YOUR-ANTHROPIC-KEY",
"models": [
{
"id": "claude-sonnet-4-6",
"name": "Claude Sonnet 4.6 via Subaiya",
"contextWindow": 200000,
"maxTokens": 8192,
"input": ["text"]
}
]
}
}
}
Replace YOUR-SUBAIYA-KEY with your sk-sub-... key from Step 2, and YOUR-ANTHROPIC-KEY with your Anthropic API key (sk-ant-...).
Using GPT models with a Codex subscription?
Add this as a second provider inside "providers":
"openai-codex": {
"baseUrl": "https://api.subaiya.com/t/YOUR-SUBAIYA-KEY",
"api": "openai-codex-responses",
"models": [
{
"id": "gpt-5.4",
"name": "GPT-5.4 via Subaiya",
"contextWindow": 200000,
"maxTokens": 16384,
"input": ["text", "image"]
}
]
}
⚠️ The "api": "openai-codex-responses" field is required since OpenClaw v2026.4.5. Without it, GPT requests may be routed incorrectly.
After saving, restart the gateway:
openclaw gateway stop && openclaw gateway start
Configure all models you want to use (e.g. GPT-5.4, Claude Sonnet, Haiku) in your OpenClaw config. Test each one to make sure it works through Subaiya. Customize your SOUL.md, IDENTITY.md, and other agent files as needed.
Take your time — the integrity monitor is inactive until you calibrate it.
Once everything is set up, go to subaiya.com/dashboard and click "Calibrate" in the Integrity Monitor section.
Subaiya will learn your system's baseline — it monitors SOUL.md, AGENTS.md, and IDENTITY.md over the next 3 messages.
After 3 messages, the monitor is active and watches for unauthorized changes to your agent's identity files.
💡 Tip: If you add new models or change agent files later, click Calibrate again to set a new baseline.
Common issues during setup and how to fix them.
Check if the gateway is running:
openclaw gateway status
If it's not running, start it with openclaw gateway start.
Check if the correct provider is active: In your OpenClaw chat, make sure the model selector shows a Subaiya model (e.g. custom-api-subaiya-com/claude-sonnet-4-6). If it shows a direct provider, your traffic is not going through Subaiya.
Verify your keys: Check that your Subaiya key (sk-sub-...) and Anthropic key (sk-ant-...) are both correct in the config.
If you see a security warning about changed files (IDENTITY.md, SOUL.md) in your first chat, this means the integrity monitor hasn't been calibrated yet.
How to fix: Go to the Dashboard, open the Integrity Monitor section, and click "Calibrate". Then send 3 messages in any chat — Subaiya learns your baseline. After that, only real unauthorized changes trigger warnings.
When to re-calibrate: After adding new models (e.g. switching from Sonnet to GPT), changing SOUL.md or IDENTITY.md, or installing new agent skills.
openclaw command not foundOpenClaw requires Node.js 22.14+ (Node 24 recommended). Install Node.js first, then:
npm install -g @anthropic/openclaw
After installation, restart your terminal and try openclaw --version.
After editing openclaw.json, you must restart the gateway:
openclaw gateway stop && openclaw gateway start
Note: In OpenClaw v2026.4.1, the raw config editor in the dashboard is disabled. Use a text editor or terminal to edit the config file directly.
A missing comma, quote, or bracket in openclaw.json will prevent the gateway from starting. Common mistakes:
} or ]Run openclaw doctor to check your configuration for errors.
401 invalid x-api-key after OpenClaw updateIf GPT models stopped working after updating OpenClaw (especially to v2026.4.5+), your openai-codex provider may be missing the "api" field.
Fix: Open ~/.openclaw/openclaw.json and add "api": "openai-codex-responses" to your openai-codex provider block:
"openai-codex": {
"baseUrl": "https://api.subaiya.com/t/YOUR-KEY",
"api": "openai-codex-responses", ← add this line
"models": [...]
}
Then restart: openclaw gateway stop && openclaw gateway start
Why: OpenClaw v2026.4.5 introduced centralized transport. Without an explicit api field, providers sharing the same base URL inherit each other's format — causing GPT requests to be sent as Anthropic format.
In the Dashboard, click your profile icon (top right) and select "Report Bug / Feedback" or "Contact Support". This sends an email directly to the Subaiya team.
Quick profiles that set all permissions at once. Switch anytime with one click.
Your agent can only read files and respond. Writing, sending messages, running commands, and deleting are all disabled. Best for when you want to observe before you trust.
Reading is allowed. Writing files, running commands, and sending messages require your approval first. Deleting is disabled. The sweet spot between safety and productivity.
Most actions are allowed without asking. Only deleting files, dangerous operations, and sensitive data access remain restricted. Maximum productivity, minimum friction.
Custom: Want fine-grained control? Change any individual permission and it automatically switches to Custom mode. You can always go back to a preset with one click.
The core of your dashboard. Every action your agent can take has one of three states.
| Status | What it means | Example |
|---|---|---|
| ON | Agent can perform this action freely | Reading files, browsing documentation |
| ASK | Agent must ask for your approval before proceeding | Creating files, running shell commands |
| OFF | Action is not available to the agent | Deleting files, accessing sensitive data |
Your dashboard organizes permissions into 20 categories — from files and terminal to email, browser, payments, and more. Click any category to expand it and adjust individual actions.
Activity Log: At the bottom of your dashboard, you'll find a log of every action your agent takes — showing which ones were allowed, which were blocked, and the details of each action (file paths, commands, etc.). You can clear the history at any time.
Your dashboard doesn't just control permissions — it actively monitors your agent for threats and anomalies.
Subaiya scans for hidden instructions in files, emails, websites, and messages that try to manipulate your agent. When an attempt is detected, you'll see an alert in your dashboard showing the source, type of attack, and details.
Critical files like SOUL.md, AGENTS.md, and IDENTITY.md are monitored for unauthorized changes. If a file is modified, deleted, or a new file appears, you'll get an alert. Click "Confirm changes" to accept intentional updates and set a new baseline.
When your agent receives images or media files, Subaiya alerts you in the dashboard. Images can potentially contain hidden instructions. Your agent is instructed to treat all media as information only — not as commands.
When using your agent in group chats (WhatsApp, Telegram, Slack, Discord), Subaiya can detect message senders and instruct your agent to only follow commands from you. Requires configuration. Contact us for setup help.
Set a spending limit per session ($5, $10, $20, $50, or custom). Track API costs in real-time with USD/EUR toggle. When the limit is reached, the agent pauses and asks you to raise it or start a new session. Only applies to pay-per-token usage.
The red STOP AGENT button at the top of your dashboard instantly blocks all agent actions. Press it again to resume. After stopping, start a new conversation in OpenClaw for a clean restart.
We're here for you. Beta means we're building this together.
Click (i) icons in the dashboard or replay the onboarding guide from your profile menu.