Agents
AI agents with a system prompt, a chosen model, scoped tools, and managed reliability.
An agent is the smallest unit of execution in Alumia. Every agent has a system prompt, a chosen model, a set of tools it's allowed to call, and a session that holds its conversation history.
Anatomy of an agent
| Field | Purpose |
|---|---|
| System prompt | Defines identity, behavior, and constraints. |
| Model | One of 37 visible models across 14 providers. Swap any time. |
| Tools | Built-in tools and connector-backed tools the agent can call. |
| Memory | Long-term context stored in pgvector and recalled per query. |
| Workspace | Org-scoped or project-scoped visibility. |
How an agent runs
Agents run on the AI SDK v6 (ai package) under the hood. Calls flow through provider-specific adapters (@ai-sdk/anthropic, @ai-sdk/openai, …) with retries, streaming, and tool-call handling managed by the platform.
When you send a message, the runtime builds the prompt, attaches available tools, streams the response, and emits canvas activity events live so collaborators see what's happening as it happens.
The default agent: Ala
Every org ships with Ala, a shared agent visible from every workspace and every project. Ala is org-scoped, active by default, and can't be deleted. Use Ala when you want a single agent that already knows about your whole org; create new agents when you want specialised behavior.