Project intelligence

Turn local project facts into better agent context.

Assura starts from deterministic paths, documents, modeled relations, and repository references, then returns a bounded context pack through the same local CLI an agent can call.

Recorded source example CLI, generator and fixture input revision: 5f7ca26de7aab9265c21b65740b431621492b8c0. Source checkout output; published release output may differ. Example output below preserves the raw generated CLI evidence.
assura content context-pack . --collection goals --id goal-portable-structure --format text
Context pack: objectdiagnostics: 0; missing relations: 0; repository refs: 0; safe fixes: 0instance: goals:goal-portable-structure (docs/goals/goal_portable_structure.md)omissions: 1

Deterministic input

Paths, documents, configured models, relations, and repository references provide inspectable source facts.

Bounded output

Context packs report their limit, omissions, diagnostics, related records, and unresolved relationships.

Local execution

The CLI produces the same context without requiring a hosted dashboard or a separate agent-specific index.

01

Facts before inference

Start from paths, configuration, documents, references, branch state, and verified content instead of asking an agent to infer project truth repeatedly.

02

Local by default

Project context stays close to the repository, can be regenerated, and can be inspected without requiring a hosted dashboard.

03

Queryable when useful

Query and context-pack surfaces organize project facts for specific workflows rather than dumping the whole repository.

04

Evidence stays visible

The response names diagnostics, omissions, relation gaps, and source paths instead of hiding them behind a summary score.

Agent setup

Set up this project with Assura.

Copy one instruction to the coding agent already working in your project. It will establish the baseline, define the expected shape, and verify it.

Agent goal Inspect, constrain, verify
Published v0.4.1. The installer provides the published release. This source checkout may contain newer changes. Keep assura and assura-full together, confirm the selected version, and follow any installer PATH correction.
First command assura agent onboard .
  1. Inspect manifests, tooling, generated output, and the intentional layout.
  2. Define project-owned rules for the expected stack. Close stable scopes so unexpected paths fail; preserve legitimate paths and ask only where evidence is ambiguous.
  3. Verify with assura review and assura check --format agent.
Installation details published release pair
curl -fsSL https://assura.dev/install.sh | sh

The copied setup instruction includes this command and the mandatory checks below.

assura --version && assura-full --version