5 MINUTE READ
Chat, agents & providers
Choose a runtime, manage conversation tabs, and understand context reporting.
Choose a provider and model
OpenCode is Loom's primary runtime. The Providers settings page also detects and connects supported local chat CLIs: Claude Code, Codex CLI, and Antigravity CLI. Availability and model choices depend on the CLI installed on your machine and its authentication state.
Choose a provider/model in the composer for a normal chat. A custom agent has its own provider and optional model configuration; selecting it routes that message to the agent's configured runtime. Check the composer before every send because a conversation can contain turns from different providers or agents.
Use a custom agent
Create or manage custom agents from the Agents settings. Configure the agent's role, instructions, provider, optional model, and enabled skills. In chat, type @ and search by its name to select it. The chosen agent's instructions and enabled skills guide that message, and the configured provider runs it.
Agent instructions do not grant additional operating-system isolation. Loom's permission policy controls supported actions, while the CLI still runs under your user account. Review requested commands and project changes.
Keep separate chats in tabs
Use the plus button above the conversation to open another chat, then select a tab to switch sessions. Each tab represents its own conversation, so you can keep separate workstreams such as backend, frontend, or bug fixing. The split-view control can show two chats side by side.
A tab remembers its session, but the composer choices are message-level controls. Confirm the selected model, thinking mode, and agent before sending when switching between workstreams.
Mention files and inspect context
Type @ in the composer to search project files and folders or select an available custom agent. Choose a file result to attach it as context; choosing a folder references that path for the provider to inspect. The provider may still need permission to read or edit files.
The context panel shows token usage when the selected provider includes usage metadata in its response. If it says that usage has not been reported, Loom has not received token counts for that turn; it does not estimate missing provider usage. Cost details are likewise provider-dependent. The Token Usage page currently summarizes chat responses; Kanban, reviews, Canvas, walkthroughs, and terminal activity do not yet have token telemetry.
Use the workspace panels
The right-side rail opens project files, context usage, changes, task activity, and the integrated terminal. The Changes panel compares files touched in the current chat. The task activity panel shows registered agents and task states. Collapse a panel when you want more room for the conversation.
The integrated terminal opens in the selected project or worktree directory and runs with your operating-system user permissions. Commands typed there are your commands; they are not automatically sandboxed by Loom. A walkthrough can turn a snapshot of uncommitted text-file changes into a guided explanation; it uses a model and reports its coverage limits.
Connect and update local providers
Open Settings → Providers to check whether a supported CLI is installed and authenticated. Select Connect to start its authentication flow; if the browser cannot launch it, use the command shown on that page in a terminal. OpenCode uses `opencode auth login`.
Use Check now to compare installed CLI versions with their latest releases. Automatic checks can be turned off. When Loom supports the provider's update flow, use Update in Loom; otherwise copy and run the official update command shown beside that provider.