The agent reads the site’s rules and skills in every session. If an agent rewrites one, every session after it follows the new text. Since Delta 0.4.2 the Context screen shows you such changes until you have looked at them.
Where it is
Open Delta → Context. When an agent has changed a rule or a skill since you last reviewed, a card called Changed by an agent sits at the top. When there is nothing new, the card is not there.
What it shows
One row per rule or skill, newest first, with what the agent did: edited one of yours, edited one of Delta’s, or made a new one. Each row has two buttons.
- Keep marks it as reviewed. The text stays as the agent wrote it, and the row goes away.
- Restore previous puts back the version from before the agent’s change. For one of Delta’s the button reads Restore theme version; for one the agent made, Move to trash.
Delta keeps the version from before an agent’s first change, so a restore is always possible. If an agent restores or deletes a rule or skill you wrote, your version goes to the trash, where you can bring it back.
Why it matters
An agent that reads a page with hidden instructions could be talked into writing them into a rule. The guardrail Confirm primary guideline changes makes it ask you first, and this card lets you check afterwards. Look at it now and then, the way you look at the Existing Auth Tokens card on Connect.
For developers
Every rule, skill, the design notes and each Memory entry carry writtenBy (agent or dashboard) and writtenAt. Text written before 0.4.2 has neither. The dashboard routes are /contexts/review, /contexts/keep and /contexts/undo.
Related: Skills, rules, and guardrails · Approvals · Security