> ## Documentation Index
> Fetch the complete documentation index at: https://docs.albus.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Private beta limitations

> What Albus does not do yet, and what to design around.

Read this before designing anything against Albus. Everything below is
deliberate scope in the private beta, not a defect, and each item changes what
you should ask an agent to do.

## Quota: 20 session runs per organization

Every invocation counts, across every session, for the lifetime of the
organization. Once the cap is reached, a run returns `429` and nothing executes:

```json theme={null}
{ "message": "organization invocation quota exceeded" }
```

Email [carlo@albus.sh](mailto:carlo@albus.sh) to have the cap raised. Do not
retry a `429` in a loop; it will not clear on its own.

## No agent memory

An agent remembers nothing outside the session it is running in. Sessions do not
share state, there is no cross-session store an agent can write to, and a run
loads at most the session's 1000 most recent messages as history.

Keep long-lived context in your own system and pass what matters in the prompt or
the system prompt.

## No code execution

The agent cannot run code, execute shell commands, or read and write files. Its
capabilities are the built-in tools (`WEB_SEARCH`) and the tools exposed by the
[MCP servers you declare](/guides/mcp-servers) — nothing else.

## No execution durability

A run that fails is not resumed or retried. If the execution environment dies
mid-run, the invocation fails and the work is lost; the API answers `502` with
the failure kind and detail.

Retrying is your call: reusing the failed run's idempotency key re-attaches to it
and returns the same failure, so start a new run with a **new** key. Keep runs
short enough that losing one is cheap.

## Limited observability

There is a [per-session audit log](/guides/audit-log) — model calls, tool calls
and their output, and run outcomes — and that is the whole of it. There are no
traces, no metrics, no dashboards, no alerting, and no cross-session search. Log
what you need on your side, keyed by session id and idempotency key.

## Roadmap

Agent memory, code execution, richer agent observability, and durable execution
are all post-beta work, along with a higher run cap. Tell
[carlo@albus.sh](mailto:carlo@albus.sh) which one blocks you — that is what
orders the list.