Context & knowledge

For an agent to do good work, it needs the right context — your standards, your project, and relevant reference material. Chronos brings these together while keeping each one in its proper place.

The kinds of context

Your organization’s standards. Company conventions, coding standards and best practices are applied to every session automatically. You don’t have to remember them or paste them in — they’re always in effect, managed centrally by your administrators, and they take precedence over anything else the agent reads.

Company prompts. Administrators write governed prompts once in the panel’s Prompts tab, and Chronos injects them into every session — regardless of which agent runs it. Update the prompt in the panel and every new session picks it up; no per-developer copies to drift out of date.

Your project’s documentation. The docs that live with your repository (such as a project guide) are part of the context, just as they are for your team. Chronos respects them as-is — they belong to your repo and stay versioned in git.

Session history. Everything that happened in a session — your instructions and the agent’s work — is remembered, so you can step away and return, and so it feeds the audit trail.

Team knowledge (opt-in). Useful lessons can be saved to carry across sessions. These are always reviewed before they’re kept — never saved silently — and they respect team boundaries, so knowledge never crosses between teams that shouldn’t share it.

Reference material. Rather than overwhelming the agent with everything at once, Chronos brings in the relevant documentation and standards as they’re needed, through approved connections (see Connected tools & data).

For the full layer model — and how the agent retrieves skills and memory on demand — see Memory & retrieval.

Inspecting a session’s context

Your organization’s context is applied to a session automatically. To see what a session received:

chronos session context <id>

The principle

Your organization’s standards are applied at run time and stay governed — they are never committed to your repository. Your project’s own documentation lives with your code. Session and team knowledge are kept by Chronos — saved deliberately and reviewably, never scattered or silently accumulated.