Tasks
A task is the main unit of work in Adam. It contains a persistent conversation, the agent’s tool activity, attached and generated files, sharing state, and any schedule bound to that work. Use one task for a connected thread of work. Start a new task when you need a clean context, a different sharing boundary, or an unrelated outcome.Turns and tool activity
Each message you send starts a turn. During a turn, Adam can reason, call tools, create or modify files, ask a question, or request approval. Some work continues in the background; the task remains the place to monitor and resume it. Task status is summarized in the task list:- Running means Adam or a background helper is still working.
- Needs input means a question or approval is waiting for someone who can respond.
- Completed means the current turn is finished.
- Scheduled means the task has an automation bound to it.
Files and outputs
Files include your uploads and outputs created by Adam. Depending on the task, they can be CAD files, code, configuration, data, documents, images, PDFs, presentations, spreadsheets, audio, or another supported type. The right-hand file panel keeps task outputs close to the conversation. The global Files page searches across tasks and lets you preview or export files.Teams
Every account operates inside a team context. A new account starts with a personal team. Shared teams add seats and member roles, and can pool plan usage across members. Team roles are Owner, Admin, and Member. A task’s sharing permissions are separate: a person invited to one task can have Can edit or Can view access without changing their team role.Integrations and live connections
An integration gives Adam access to another system. Connection state means different things for different systems:- Onshape is a durable OAuth account connection.
- Fusion is live while the add-in is running and connected to the open Fusion session.
- Desktop applications are live while the paired desktop connector and target application are running.
- Arena and other cloud applications use their own authenticated connection.
A connected account does not always mean a local application is currently available. Fusion and desktop-connected applications require a live application session when Adam needs to inspect or modify it.