Concepts

superglue organizes work into a few building blocks. The sidebar follows the same order: agent sessions and projects at the top, then the brain, the capabilities, and the control panel.

Agent sessions

A session is a conversation with the agent. You describe the outcome, the agent plans, reads client data, builds and tests tools, and asks for approval before writing to a client system. Sessions can belong to a project or run on their own.

Projects

A project is one engagement. It holds tasks with status, owners and due dates, and it links the tools and files involved. Sessions started in a project prioritize that context. See Project setup.

Brain

The brain is what superglue knows about your work: connected context sources such as meeting notes, Slack, Teams and email; uploaded files such as client exports and your templates; playbooks that hold your methods; and artifacts the agent has produced. See Project context.

Connections

A connection is one authenticated account for an API, database, file server or other service, for example “Contoso sandbox”. It stores the URL, the authentication method, the secret values, an optional secure gateway and usage notes. Secret values are encrypted and never appear in agent prompts. Connect a service by describing it to the agent; the agent configures the connection and asks for secret values in a secure form. Manage connections and reusable OAuth apps on the Connections page.

Each connection has a system ID such as netsuite or acme_billing. Tools refer to the system ID, not to one connection, so the same tool runs against a sandbox or a production account without changes. A run uses the connection selected for it, or the user’s default connection for that system ID.

Tools

Tools are saved, repeatable actions: a migration load, a nightly sync, a reconciliation query. The agent builds and tests them with you. A saved tool runs the same steps every time with no AI at execution time. Tools run on demand, on a schedule, from a webhook, from the API, or through an MCP server.

Artifacts

Artifacts are the documents the agent produces: data assessment reports, mapping proposals, questionnaires, reconciliations and spreadsheets. They live in Brain next to your uploaded files. They download as PDF, Word, HTML or Excel and can be shared with a client through a link.

Runs

Every tool execution creates a run with its trigger, user, connection, input, step results, timing and errors. Runs are the audit trail and the starting point for investigating a failure. See Monitoring runs.