App Studio private preview
Upcoming / private preview
App Studio is controlled by a feature flag while the assistant surface is completed and tested. Registered Apps, API keys, MCP clients, Semantic Search, RAG in a box, Usage, Audit Log, and AgentGrid remain available without App Studio.
App Studio is the upcoming Slab5 console surface for building against workspace records with an assistant. It is designed to help a builder create, query, preview, and manage Slab5 records while staying inside the current workspace, app identity, scopes, and approval rules.
Assistant capabilities can be enabled per workspace only when Slab5 has enabled the private preview. Registered Apps remain available as app identities for API and MCP integrations even when App Studio is hidden.
What App Studio does
App Studio is useful when a builder wants to turn a product idea, app setup task, or workspace operation into concrete Slab5 records.
Common tasks include:
- creating or previewing CMS entries, campaigns, tasks, support tickets, approvals, apps, and draft workflows
- checking which App Studio tools are ready for the selected workspace and app context
- reviewing generated artifacts before using them
- proposing approval-gated handoffs before workflow runs or operational writes happen
- creating draft AgentGrid agents and a draft workflow from an assistant conversation
App Studio should not be treated as an unrestricted browser or cloud automation agent. It executes only the actions exposed by the Slab5 workspace context and its available tools.
Console areas
| Area | Use it for |
|---|---|
| App Studio | Private-preview assistant surface for conversations, artifacts, tools, and handoffs when the feature flag is enabled. |
| Registered apps | Manage custom app identities, requested scopes, client IDs, origins, callbacks, usage, audit attribution, app-associated keys, and optional Vector/RAG ownership. |
| Connected Slab5 apps | Review Slab5-managed first-party app installations connected to the account. |
Registered app identities are separate from workspace API keys. An app identity describes the application; a workspace credential or grant controls what that app can do in a workspace.
If App Studio is disabled, use Registered Apps for app identity, API Keys for credentials, RAG in a box for developer-managed retrieval collections, and AgentGrid for governed workflow execution.
Assistant conversations
App Studio conversations are scoped to the selected account, workspace, and optional app context. The assistant can answer setup questions and propose actions using available Slab5 tools.
The console supports:
- creating a new general conversation
- loading previous conversations
- renaming or archiving conversations
- using a split view with the assistant on one side and artifacts/tools on the other
- showing missing scopes when a selected app does not yet have enough workspace access
When a conversation is tied to an app, App Studio can use the app key, workspace ID, account ID, and tool context to decide which actions are available.
Artifacts and tools
Artifacts are reviewable outputs created by App Studio. Examples include draft workflows, generated content, app setup material, support-ticket drafts, task plans, and other workspace records prepared for review.
The tools panel shows available App Studio tools grouped by module. Each tool should make its availability clear:
- available
- missing scope
- unavailable for the current workspace or app context
If scopes are missing, a workspace owner or admin can grant the app the required scopes before trying the action again.
When a workspace owner has connected and approved external MCP tools in AgentGrid, App Studio can see the approved executable tool names, descriptions, schemas, and risk levels after Slab5 applies connection policy. External tool execution still runs through the Slab5 broker, approval state, risk policy, and confirmation checks. See External MCP tools for the connection model.
Registered apps
Registered apps give builders a stable identity for custom apps that use Slab5.
Use Registered apps to review:
- app name and app key
- client ID
- app type and status
- requested scopes
- allowed origins and callbacks
- associated API keys
- usage event counts
- audit event counts
For production apps, keep requested scopes narrow. Grant only the modules and actions that the app needs in the selected workspace.
See Registered Apps for the current general-availability app identity model, including app filters in Usage and Audit Log, app-associated API keys, app-level rollups, app budget metadata, and optional Vector/RAG collection ownership.
Safety boundary
App Studio is intentionally bounded:
- External publishing, sending, deployments, cloud changes, and arbitrary connected-tool execution require explicit connector setup.
- Approval-gated actions require an explicit confirmation before records are created or workflow handoffs run.
- Publishing, running, and scheduling draft AgentGrid artifacts happens from AgentGrid after review.
- App Studio follows tenant, workspace, module, scope, billing, and audit controls like the rest of the control plane.
Use App Studio to accelerate setup and drafting. Use AgentGrid for governed workflow execution, approval history, schedules, and run logs.