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 systems, 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 systems, files, playbooks and artifacts 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.

Systems

Systems are the connections to APIs, databases, file servers and other services. Each system stores the endpoint, the authentication method, the required secret names and the documentation the agent uses. One system serves many clients through separate credentials. See Client systems.

Credentials

A credential is a named set of secret values for one system, for example “Contoso sandbox”. Secret values are encrypted and never appear in agent prompts. A run uses the credential selected for it or the user’s default credential for that system.

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: discovery reports, mapping proposals, questionnaires, reconciliations and spreadsheets. 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, credential, input, step results, timing and errors. Runs are the audit trail and the starting point for investigating a failure. See Monitoring runs.