Help centre · Understanding

How do I explain my internal conventions to the agents?

Write what a new joiner would need explained, so every run knows it.

Preferences → My contexts lets you write, in plain prose, what the agents cannot guess: your in-house library, your naming conventions, the traps in your codebase. These texts go into every run, on top of the technology's rules.

What belongs in there?

The simplest test: what would I explain to a capable developer joining this project on Monday? That is exactly what the agents need.

What works well:

• "All our API calls go through ApiClient, never fetch directly."
• "User-facing labels live in lang/, never hardcoded in a view."
• "The invoices module is being rewritten: do not touch it without saying so."

What is useless: restating the framework's own conventions. Diavi already knows those — that is what you are buying.

Why one context per repository?

Because two repositories do not share conventions, even on the same technology. What you write about one client's module must not reach runs on another client's repository.

The left column lists All my repositories, for what does not depend on any repository (your review habits, your ticket convention), then the repositories that already have a context. Add a repository lets you pick one from your forge's list.

A run loads All my repositories plus the repository it works on, never the others.

If you had filed contexts by technology, they appear under Former filing by stack: they still reach that technology's runs, but no new file can be created there. Copy them into a repository or into All my repositories, then delete them.

Is there a size limit?

Yes, 40,000 characters for what a run actually loads: All my repositories plus one repository. The gauge shows that total for the open scope. It is not arbitrary: this text goes into every call of the run, so its size shows up directly in your usage. The interface refuses to save beyond it rather than truncating silently.

Who can edit them?

The account owner and administrators. A context enters every prompt: it is a cost lever, not a comfort setting.

Do I see Diavi's own rules?

No. Each technology's rules are Diavi's craft and stay private. Your contexts are added to them; they never replace them, and you keep receiving their updates.