Every run starts with what CodeLynq already knows about your codebase: where things live, the conventions you follow, decisions you made and traps to avoid. This memory grows by itself as runs learn, and you can add to it yourself.
Where the knowledge comes from
Each run reads, in this order:
- Organization standards - rules that apply to every project in the organization.
- Project memory - facts that apply to the whole project.
- Repository memory - facts about one specific repository.
Together with the project's context and conventions, this is what a run knows before it writes any code.
How memory grows
After a run, CodeLynq notes new, lasting facts it learned about the codebase - for example that a certain folder holds all API handlers, or that the tests need a particular setup. Reviewer feedback on pull requests is a source too. These entries are marked learned. Learned entries can be cleaned up automatically over time; notes you add yourself are kept.
View and edit the memory
Open the project and go to Settings → Memory. Entries are grouped under Project-wide and one group per repository. Each entry shows its kind - structure, convention, gotcha, decision or other - and whether it is pinned (added by a person) or learned.
Organization admins and the project's owner can:
- Add note - choose the Kind, the Scope (Project-wide (all repositories) or one repository) and write the Content, then click Add note. Notes you add are pinned and never removed automatically.
- Edit or Delete any entry - for example a learned fact that is wrong or no longer true.
Write a note so it makes sense on its own, for example: "Auth tokens are validated in app/core/security.py - never duplicate that check in handlers."
Organization standards
Rules that should hold for every project - the things you would otherwise repeat in every code review - belong in the organization's standards.
- Go to Settings (under Organization in the sidebar) → Standards.
- Click Add rule, choose a kind (Convention, Decision, Gotcha, Structure or Other) and write the rule in one or two sentences.
- Save it. Each rule can be edited or removed later.
Only organization admins can add, edit or remove standards; other members can read them. Every rule is sent with every run, so the list has a maximum length - combine related rules to keep it focused.
Tips
- Correct wrong facts as soon as you notice them: a wrong memory entry affects every following run.
- Use memory for facts about the code; use the task or the spec for things that only matter to one piece of work.
- Organization standards suit cross-project rules ("every endpoint writes an audit log entry"); project context suits a project's stack and architecture.