Console
Manage projects, keys, memories, evaluations, webhooks, members and settings from the browser.
The console lets you manage your projects and memory from the browser: connection setup, API keys, inspecting memories, a playground, evaluation, webhooks, export/import, members and settings. On the hosted service open https://memory.empecta.com, which takes you to the console at /app/. A local install serves it at http://localhost:5199/app/.
Signing in
| Environment | How you sign in |
|---|---|
| Hosted / production | Google, Microsoft (OIDC) or a one-time code sent to your email. The sign-in page shows which of these are enabled. |
| Local Development | Passwordless developer sign-in; works only from the same machine (loopback). |
On first sign-in you complete the onboarding steps (accepting the terms, creating an organization and a first project). Invited users join the organization with an invitation code.
Self-hosted
The console UI is served prebuilt. If you run from source, build it in AgentMemory.App with npm ci && npm run build (or use the development server with npm run dev).
Pages
URL structure: /app/<organization>/<project>/<page>, on the hosted service and on a local install alike.
Setup
| Page (menu label) | What you do there |
|---|---|
| Install | Pick your client and get ready-made MCP connection settings, plus Claude Code plugin and SDK setup info. You can create an application-specific connection URL. |
| Playground | Add messages (with extraction or verbatim), run searches, and see why results came back and what was cut by the token budget. This is the only write path that can set an expiry (expiresAt) and tags. |
| API Keys | Create and revoke keys: application binding, permissions, bound agents, act for users, expiry date. A key is shown once. |
Activity
| Page | What you do there |
|---|---|
| Dashboard | Overview of the project. |
| Requests | API request log (status, duration) and the change feed. |
| Entities | End users and entities extracted during consolidation; memories linked to an entity. Edit user profiles. |
| Memories | Memory explorer: filtering (application, facet, type …), detail drawer, explain, history, supersession chain, content correction, sharing (tenant admin), deletion, good/bad rating. |
| Evaluations | Saved recall tests and run history. See Evaluation. |
| Curation | Blocks, manually triggering consolidation, background job status, learning indicators. |
| Graph | Relationship graph between memories, colored by application. |
| Webhooks | Create subscriptions, test, delivery history, rotate secrets, requeue dead deliveries. See Webhooks. |
| Export & Import | Export a project as JSON and import it. See Data management. |
The Curation, Graph, Webhooks and Export & Import pages depend on your plan including these features; if it doesn't, they appear locked in the menu.
Account and settings
| Page | Contents |
|---|---|
| Settings → Project → General | Project name; LLM provider and your own API key (BYOK), with a connection test. |
| Settings → Memory Extraction | Extraction and consolidation settings. |
| Settings → Categories | Categories: which types get promoted, and extraction instructions. |
| Settings → Retention | Retention periods. |
| Settings → Organization | Organization name, deleting projects, closing the organization (offboarding). |
| Settings → Members | Invitations, roles (tenant-admin, member), per-project access. |
| Settings → Promotions | Approve/reject tenant-wide rule candidates (including approving as a floor). |
| Settings → Audit Log | Console audit log. |
| Settings → Profile | Personal settings; sign out of all your sessions. |
| Usage & Billing | Usage, plan and billing. |
Console settings are stored at the workspace or tenant level and override the defaults in the server configuration. For setting keys, see Configuration.