Features

Context Editor

The Context Editor lets you define exactly what your agents know, what they can touch, and what they must not break — without writing YAML or prompt files. It's version-controlled and shared across your whole team.

Focus windows

A focus window tells an agent which files and directories it is allowed to modify. Agents cannot write outside their focus window — the Orchestrator blocks any such attempt.

include: src/api/auth/**
include: src/middleware/**
exclude: src/api/auth/oauth.ts  # do not touch OAuth

Constraints

Constraints are rules the agent must not violate. They are checked by the Orchestrator on every Shard before merge. Examples:

• No new npm dependencies — agent cannot add to package.json
• No hardcoded secrets — Orchestrator runs secret-scan on every diff
• Tests must pass — Shard is rejected if the test suite fails
• API contract must not change — existing endpoints cannot change signature

Success criteria

Success criteria tell the Orchestrator what done looks like for a given task. The Orchestrator uses these during the audit phase to check whether the Shard actually solved the problem, not just whether it compiles.

Version control

Every context change is committed to the repo as a .alfred/context.yml file alongside your code. Roll back, diff, and review context the same way you review a PR. Every developer and agent on the project always sees the same context — no diverging mental models.