# Engram Web Console

The Engram console is a graphical interface for inspecting and managing your Engram projects in [Weaviate Cloud](https://console.weaviate.cloud). Browse memories, users, and runs, manage API keys, and review your project's groups and topics, all without writing code.

To open it, sign in to [Weaviate Cloud](https://console.weaviate.cloud), select the **Engram** product from the top navigation, and choose a project. The left-hand menu gives you access to the **Dashboard**, **Users**, **Memories**, **Runs**, **API Keys**, and **Plans** pages.

## Dashboard

![Engram console dashboard](/assets/docs/engram/_includes/console/dashboard.png)

The dashboard is the overview for the selected project. The top of the page shows your current plan and usage for the period, including how many [runs](../engram-concepts/pipelines.md#runs) you have used against your monthly cap.

The summary cards report the project's totals: memories, users, API keys, and runs in the last 24 hours.

The **Groups** section lists the project's [groups](../engram-concepts/groups.md) and the [topics](../engram-concepts/topics.md) in each one. For every topic you can see its description and its [scope](../engram-concepts/scopes.md) requirements, such as `user` or `conversation_id`. Use **Edit Group** to review a group's configuration.

:::callout{intent="note"}
Groups and topics are defined when a project is created. Editing them in the console is read-only for now, and creating new groups from the console is coming soon.
:::

## Users

![Engram console users page](/assets/docs/engram/_includes/console/users.png)

A [user](../engram-concepts/scopes.md) is created automatically the first time a memory is written with a new `user_id`. The Users page lists every user in the project.

Each row shows the user's name (`user_id`), when it was created and last updated, how many memories and conversations it has, and when it was last active. Use the action on the right of a row to delete a user and its memories.

## Memories

![Engram console memories page](/assets/docs/engram/_includes/console/memories.png)

The Memories page lists the [memories](../engram-concepts/memories.md) stored in the project. The **Activity** tab shows recent memories, and the **Search** tab lets you run a query against them.

Filter the list by group, topic, user, or conversation using the dropdowns at the top. Each row shows the memory's ID, topic, group, user, properties, and when it was last updated. Use **Create Memory** to add a memory directly from the console.

![Engram console memory detail panel](/assets/docs/engram/_includes/console/memory-detail.png)

Select a memory to open the **Memory Detail** panel. It shows the memory's full content along with its topic, group, user, [properties](../engram-concepts/scopes.md), and created and updated timestamps.

Use **Delete memory** in the panel to remove a single memory.

## Runs

![Engram console runs page](/assets/docs/engram/_includes/console/runs.png)

Every time content is sent to Engram, it runs through an asynchronous [pipeline](../engram-concepts/pipelines.md) that can create, update, or delete memories. Each of these executions is a [run](../engram-concepts/pipelines.md#runs).

The Runs page lists recent runs and lets you filter by status. Each row shows the run ID, status, input type, user, the number of memory operations, and when it started and finished.

![Engram console run detail panel](/assets/docs/engram/_includes/console/run-detail.png)

Select a run to open the **Run Detail** panel. It shows the run's status, input type, user, group, and starting step, along with timestamps.

The memory operations section lists the memories the run created, updated, or deleted, so you can trace exactly what changed.

## API Keys

![Engram console API keys page](/assets/docs/engram/_includes/console/api-keys.png)

API keys authenticate your application with a project. The API Keys page lists each key by name, with its key prefix, when it was created, and when it was last used.

Use **Create Key** to generate a new key. The full key is shown only once, so copy and store it securely. Use the action on the right of a row to delete a key.

## Plans

The **Plans** page shows your current plan and lets you upgrade. Your plan determines limits such as the number of pipeline runs allowed per month. When a free plan reaches its monthly run cap, new runs are rejected until the cap resets.

## Questions and feedback

Have a question or feedback? Here's how to reach us.

::::card-grid
:::card{title="Community Forum" href="https://forum.weaviate.io/c/support" icon="messages-square"}
Ask questions and connect with other developers on our **Community forum**.
:::

:::card{title="Support" href="/guides/support-overview" icon="life-buoy"}
Weaviate Cloud user or customer? Find the right channel on the **Support page**.
:::
::::

## Related pages

- [Agents](./agents-index.md)
- [AI-assisted Weaviate code generation](./ai-assisted-vibe-coding-index.md)
- [APIs](./apis-index.md)
- [Authorization and authentication](./authorization-and-authentication-index.md)
- [Benchmarks](./benchmarks-index.md)
- [Best practices](./best-practices-index.md)
- [Client libraries](./clients-index.md)
- [Client Libraries / SDKs](./client-libraries-index.md)
- [Cloud](./cloud-index.md)
- [Cloud account management](./cloud-account-management-index.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.
