Workflows

From a request
to a controlled result.

Conversation, projects, files, agent tasks, structured data, review, and feedback stay connected inside one general-purpose workflow.

Follow the Workflow →Open Interactive Tour
Workflow 01 · Surfaces

What you touch.
Not what routes it.

Routing internals are on the Platform page. This is the operator side: the surfaces a request actually moves through, and what each one is for.

01
Enter
Chat or Project
Work starts in a chat session, or inside a project that carries its own files, context, and history across sessions.
sessions · projects · persistent context
→
02
Attach
Files + Data Grid
Uploaded or connected structured data can be inspected, profiled, queried, charted, and exported inside the workspace.
upload · schema · query · export
→
03
Delegate
Agent Subtasks
Work that decomposes can be handed to dynamic agents running their own subtasks, each visible as it progresses rather than as a single opaque call.
dynamic agents · parallel subtasks
→
04
Control
Action Previews
Operations with real-world effect surface a preview the operator must approve before anything executes — not a silent action taken on their behalf.
preview · explicit approval
→
05
Inspect
Traces
Every dispatch — a routed reply, an agent subtask, a fallback — is recorded as a trace the operator can open, not just a result with no history behind it.
dispatch · latency · outcome · errors
→
06
Close the loop
Ratings
A thumbs up, thumbs down, or written note becomes routing evidence — the mechanism behind it lives on the Platform page's Karma system.
explicit feedback · routing evidence
Workflow 02 · Connected Surfaces

What stays connected
while the work moves.

Chat, projects, files, agent tasks, Data Grid operations, traces, approvals, and ratings share one operating context instead of becoming separate manual handoffs.

Without orchestration
  • The operator chooses a provider before the work is understood
  • Provider limits and outages interrupt the workflow
  • Context is scattered across sessions and project tools
  • Subtasks are manually copied between specialist models
  • Quality feedback is disconnected from future routing
  • High-risk actions lack a consistent review boundary
Agent Forge
  • Live discovery across the providers and runtimes you configure
  • Routing considers capability, health, limits, latency, and evidence
  • Three core slots plus a wider pool for agents and subtasks
  • Persistent sessions, projects, checkpoints, and vector retrieval
  • Trimurti review, Rta signals, decision traces, and user ratings
  • Action previews and approvals for operations that need control
  • Optional authenticated endpoints for user-owned GPU runtimes
  • Data Grid workflows for uploaded or connected structured data
  • Fallbacks are attempted only when a compatible backend is healthy