Choose your Console starting point, connect your operations systems, and understand the services behind agent execution.
StateSet Console brings agent conversations, integrations, autonomous sessions, and operational
activity into an operator interface. Use the web app to configure your workspace and verify a
first task, then use mobile to access the Console from your phone.
For an existing deployment, obtain its URL or app build, a supported sign-in method, and access
to the intended organization. Connect only the business systems needed for your first task.
An integration catalog entry is not the same as a configured and verified connection.For a self-managed or development Console, configure these service boundaries:
Service
Responsibility
First verification
Authentication
Sign-in, session validation, and organization access
Sign in and complete any required verification or provisioning
Persistence
Hasura-backed application data
Verify server configuration and authorized data access
Execution
Direct Sandbox or an orchestration-to-sandbox path
Inspect /api/ready for the selected backend, then run one bounded task
Model and tools
Model access plus organization integration/MCP credentials
Inspect a real tool result for a known test record
Keep backend credentials server-side. Follow the
web setup walkthrough
and the repository’s linked configuration guide for the selected execution path.
Choose a record you can independently inspect, such as a test order or ticket. Ask the Assistant
to read its current state without making changes. Compare the tool result and answer with the
source system, and save the conversation or session identifier.Once that works, expand to a workflow with explicit scope, connected tools, approval requirements,
and a verified stop procedure. A successful login, an approval, or a disconnected stream alone
does not establish that a business operation completed.
Web and mobile use the Console backend. Desktop connects to the Engine and has its own native
credential and MCP connection surfaces. Confirm each client’s deployment and organization;
do not assume credentials, cached views, or session lists are interchangeable across clients.
