Workspace Setup
Review workspace settings, verification, and connection status.
Verified
Core verification checks passed and operator access looks ready.
Core instance checks passed and operator access looks ready.
Last checked Jun 4, 12:39:31 AM (server time)
Test your connection
Node
npm install osuite
import { OSuite } from 'osuite';
const osuite = new OSuite({
baseUrl: process.env.OSUITE_BASE_URL,
apiKey: '<YOUR_API_KEY>',
agentId: 'my-agent',
});
const { action_id } = await osuite.createAction({
action_type: 'test',
declared_goal: 'Verify OSuite connection',
});Python
pip install osuite
from osuite import Osuite
osuite = OSuite(
base_url="<YOUR_BASE_URL>",
api_key="<YOUR_API_KEY>",
agent_id="my-agent",
)
osuite.create_action(
action_type="test",
declared_goal="Verify OSuite connection",
)cURL
curl -X POST https://studio.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 lifecycle hooks, 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 emits local hook and approval events while OSuite preserves replay, proof, and tenant-visible 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
ChatGPT Apps Governed Connector
Best for ChatGPT Apps deployments where OSuite opens the governed action and approval path before work continues, while final closure is reported by the connector or reconciled from runtime session state.
Governance range: l2 -> l3
Surface path: connector + control-plane
Approval: OSuite preflight review with connector-reported closure
Evidence: Connector-declared action metadata with OSuite decision receipts
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.