Console

What is the Areev Console?

The Areev Console is an open-source web application built with Angular 21, Tailwind v4, and PrimeNG that provides a visual interface for operating the Areev context database.

The Console connects to a running Areev server over its HTTP API and exposes its functionality through a memory-scoped sidebar grouped into four sections — EXPLORE, OPERATE, GOVERN, and BUILD. After picking a memory the sidebar surfaces: under EXPLORE, Memory (grains, graph, and timeline as three sibling pages), Knowledge Sources (document import and connector sync), CAL Studio (query authoring), and Harness (configure agent harnesses); under OPERATE, Health (system status) and Intelligence (computed metrics); under GOVERN, Compliance (regulation checks and policies) and Audit (hash-chained event log with provenance); under BUILD, Integrate (HTTP / gRPC / MCP / A2A / CLI / SDKs / Guides / Notebooks reference as sibling routes) and Hooks (webhook + inbound-connection management). Chat is the implicit landing page when you open a memory — it lives at /memories/:id and is not a sidebar entry of its own. Each view maps directly to the underlying REST endpoints, so anything you do in the Console can also be done via the API or CLI.

The Console ships as a standalone Angular application with no server-side rendering. It uses Angular 21 standalone components and signals for state management, Tailwind v4 for styling, and PrimeNG for data tables, dialogs, and form controls. The autonomous memory engine exposes all operations through the same /api/ endpoint prefix that the Console consumes, making it straightforward to build custom integrations alongside the Console.

How do I open the Console?

Sign in at app.areev.ai and pick the memory you want to operate on — the Console is hosted by Areev and served from your org’s CDN.

For Areev cloud customers, the Console is delivered through Azure Front Door at https://app.areev.ai and routes API calls to your org subdomain (https://<org>.areev.ai). There is nothing to install or run — sign in with your organization account and the Console opens against your live cells.

What views does the Console provide?

Every Console view lives under /memories/:memoryId/ and is its own standalone Angular route — no view nests inside another’s tab container; the EXPLORE / OPERATE / GOVERN / BUILD groups exist in the sidebar only, not in the URL hierarchy.

Chat — /memories/:id is the default landing page (a command-centre home); sending a message activates /memories/:id/chat (or /memories/:id/chat/:threadId for an existing thread) with a conversational interface for querying memory.

Memory — The memory explorer has three tabs reached via sibling routes: Grains (/memories/:id/grains, searchable table), Graph (/memories/:id/graph, knowledge-graph visualization), and Timeline (/memories/:id/timeline, chronological view). Drag-and-drop document upload lives on its own top-level page at /memories/:id/knowledge-sources.

Harness — /memories/:id/harness lists the agent harnesses bound to the memory. /memories/:id/harness/new runs the create wizard; /memories/:id/harness/:slug opens the harness with its Configure surface as the default, and /memories/:id/harness/:slug/configure and /memories/:id/harness/:slug/activity are sibling routes for editing the harness config and inspecting recent runs and feedback.

CAL Studio — /memories/:id/cal-queries is the canonical query authoring surface and /memories/:id/cal-templates is the sibling template authoring surface. /memories/:id/cal-studio is preserved as a redirect alias to /memories/:id/cal-queries for legacy bookmarks.

Health — /memories/:id/health shows system status, overview metrics, security and compliance posture, and subsystem status.

Intelligence — /memories/:id/intelligence monitors computed metrics across operational domains.

Compliance — /memories/:id/verify runs automated compliance checks across regulations and /memories/:id/policies is a sibling route for managing governance policies.

Audit — /memories/:id/audit displays a hash-chained, tamper-evident event log and /memories/:id/provenance is a sibling route for provenance lookups against the same chain.

Integrate — API reference documentation, SDK guides, Colab notebooks, and connection examples across HTTP, gRPC, MCP, A2A, and CLI interfaces are served as sibling routes (/memories/:id/sdks, /http, /grpc, /mcp, /a2a, /cli, /guides, /notebooks — see the Notebooks cookbook). /memories/:id/integrate[/<tab>] redirects to the matching sibling for legacy bookmarks.

Hooks — A two-tab surface for event-driven integrations. /memories/:id/hooks manages outbound webhook subscriptions (signed delivery to your endpoints), and /memories/:id/connections manages inbound Axtion-style connectors that bring external events and data into the memory.

Each view is implemented as a standalone Angular component with its own route, making the Console modular and extensible. The views communicate with the server through Angular’s HttpClient and specialized services like ComplianceService, ChatService, and ChatThreadService that wrap REST API calls with typed request and response models.

  • Memory: Search, browse, visualize, and import grains
  • Compliance: Compliance checks, policy management, and audit trails
  • Ingest: Document upload and import
  • Health: System monitoring dashboard