Skip to main content

User guide

Choose how you work

Every Fabric interface uses the same profile-scoped agent core. Pick the surface that fits today's task; model routes, memory, skills, approval policy, and sessions stay with the profile.

Open the first-run guide Configure a model

Pick a surface​

Visual workspace

See the work as it happens​

Use the native app for focused chat and project work, or open Fabric Workspace and Admin for browser-based operations and runtime control.

Use Desktop → · Understand Workspace and Admin → · Run the web experience →

Terminal

Stay close to the repository​

Use the CLI for direct work and scripting, or the TUI for an interactive full-screen terminal experience.

Use the CLI → · Use the TUI →

Messaging

Keep a conversation available​

Connect a supported channel for long-running conversations, scheduled delivery, and remote access.

Set up messaging →

Understand the two web surfaces​

  • Workspace is where business users follow conversations, agents, design briefs, persistent work, automations, evidence, and outcomes.
  • Admin is where operators configure integrations, channels, models, credentials, and the Fabric runtime.
  • Profiles remain independent agent configuration and memory islands. They are not tenant, team workspace, site, or human-role scopes.

The shell, Home, Design, persistent Chat, and SQLite-backed Work surface are available now. Chat's Task, Evidence, and Artifacts tabs are best-effort views of the existing terminal event stream, while Memory reports provider and configuration status. Enterprise tenancy, server-enforced roles, durable approvals, unified activity, and a provider-neutral typed Memory service remain staged backend contracts. See the Workspace and Admin guide for the route map and current delivery status.

Shape the agent around your work​

Remember the right context​

Use profile-local memory for durable facts and project context files for instructions that belong with the work.

Understand memory → · Add project context →

Add focused capabilities​

Skills load task-specific playbooks on demand. Tools and plugins connect services without turning every workflow into core behavior.

Work with skills → · Configure tools → · Extend with plugins →

Automate repeatable work​

Schedule jobs with cron, split larger tasks with delegation, and use checkpoints before risky changes.

Schedule a job → · Delegate work → · Use checkpoints →

Separate and secure environments​

Use profiles to isolate credentials and state, then review approval and network boundaries before remote or unattended operation.

Manage profiles → · Review security → · Store secrets →

A reliable first session​

  1. Select one route. Run fabric model and configure only the provider you intend to test.
  2. Verify the profile. Run fabric status --deep before opening a long session.
  3. Prove one task. Ask Fabric to complete a small, observable action, then add memory, skills, or another surface.

For the exact commands and verification criteria, follow the Quickstart. For configuration keys and command syntax, use the Reference.