Settings
Workspace configuration, runtime verification, account controls, and operator setup.
Track how well this workspace converts runtime activity into governed checkpoints, approvals, and proof.
This strip updates from live workspace evidence so operators can see whether the portable control plane is actually covering actions end to end.
Ready but not fully verified
Core checks are passing, but deeper validation or operator follow-up is still pending.
This page separates what has already been verified from live validation that is still pending.
Last checked Apr 20, 01:53:07 PM (server time)
Test your connection
Node
npm install osuite
import { OSuite } from 'osuite';
const claw = new OSuite({
baseUrl: process.env.OSUITE_BASE_URL,
apiKey: '<YOUR_API_KEY>',
agentId: 'my-agent',
});
const { action_id } = await claw.createAction({
action_type: 'test',
declared_goal: 'Verify OSuite connection',
});Python
pip install osuite
from osuite import Osuite
claw = OSuite(
base_url="<YOUR_BASE_URL>",
api_key="<YOUR_API_KEY>",
agent_id="my-agent",
)
claw.create_action(
action_type="test",
declared_goal="Verify OSuite connection",
)cURL
curl -X POST https://docs.osuite.ai/api/actions \
-H "Content-Type: application/json" \
-H "x-api-key: <YOUR_API_KEY>" \
-d '{"action_type":"test","declared_goal":"Verify OSuite connection"}'Runtime approval profiles
Claude Code Local Runtime
Best for local operator sessions that need interactive approvals and governed tool call evidence at the execution boundary.
Governance range: l2 -> l3
Surface path: runtime-adapter + control-plane
Approval: Terminal-first approval channel
Evidence: Built-in governed tool provenance
Codex Governed Runtime
Best for governed coding sessions where Codex is the active runtime orchestrating tools and approvals.
Governance range: l2 -> l3
Surface path: runtime-adapter + control-plane
Approval: Inline operator approvals in the coding session
Evidence: Codex-reported governed tool metadata
OSuite SDK Service Runtime
Best for self-built or embedded agents that report governed actions through the OSuite SDK.
Governance range: l1 -> l2 -> l3
Surface path: embedded-sdk + control-plane
Approval: Server-mediated approval handoff
Evidence: SDK-declared agent and tool metadata
These runtime profiles describe how approvals and evidence behave. They do not replace the choice between self-hosting and a future SaaS control plane.
Configure one governed setup flow that still works across different agent runtime families.
Setup should describe Runtime checkpoints, boundary semantics, and Replay-ready evidence in the same language operators will see later in routing, policy, and evidence views.
Make verification, human review, and control handoffs explicit before agents begin executing.