Using BetterContext Copy

Using BetterContext: Overview

A guide to the BetterContext dashboard, team workspace management, and integrating memory into daily developer workflows.

BetterContext is designed to live invisibly alongside your existing tools. Whether you interact through our cloud dashboard, local terminal CLI, or directly inside your IDE, the system maintains a unified context layer across your entire engineering team.

The Web Dashboard

The BetterContext Web Console (app.bettercontext.dev) provides high-level observability and administrative controls:

Knowledge Explorer: Visually traverse your organization's memory graph, inspect entity relationships, and audit confidence scores.
Activity & Telemetry: Monitor agent queries, cache hit ratios, token savings, and latency metrics in real time.
Policy Engine: Configure role-based ACLs, redact proprietary secrets, and define negative constraints.

Workspaces & Environments

Workspaces represent independent organizational boundaries:

Multi-Tenant Isolation:
• Production Workspaces: Contain canonical repositories, architecture specs, and production runbooks.
• Staging / Sandbox Workspaces: Safe environments for testing new autonomous agents and custom experimental skills.
• Departmental Workspaces: Isolate engineering codebases from marketing or financial documents with strict permission walls.

Daily Developer Workflow

Morning Triage: Coding agents automatically query the memory graph for recent PR merges and breaking schema updates.
Active Development: In Cursor or Claude, agents generate code that adheres strictly to your team's documented conventions without prompting.
Automated PR Reviews: CI agents evaluate proposed PRs against the experience engine's historical bug resolutions.

Next Steps

Was this page helpful?

ON THIS PAGE

Overview
Web Dashboard
Workspaces & Isolation
Developer Workflow
Next Steps