| name | chronicle-context |
| description | Use when the user asks to use Chronicle, screen context, recent screenshots, live screen awareness, or ambient context to understand what they are working on, critique an open artifact, or continue from visible state. |
Chronicle Context
Use this carefully. Screen context can be powerful and invasive.
When To Use
Good fits:
- The user explicitly says to use Chronicle or screen context.
- They want feedback on something currently visible.
- They need continuation from an open slide deck, browser page, design, or app state.
- They ask, "what should I add to this?" while the artifact is on screen.
Avoid by default:
- Private messages, banking, health, legal, or unrelated personal screens.
- Sensitive third-party data.
- Situations where normal file/context access is enough.
Workflow
- Confirm the user wants screen context if the request is ambiguous.
- Inspect the freshest relevant screen state.
- Summarize only task-relevant observations.
- Use visible context to make recommendations or continue work.
- Do not store screen-derived private information in skills or durable project memory unless the user explicitly asks.
Privacy Rules
- Treat screenshots as sensitive.
- Minimize what you quote or repeat.
- Do not infer personal facts beyond the task.
- Do not use Chronicle as a replacement for asking when the visible state is unclear.
- If sensitive content appears incidentally, ignore it and continue with only the requested surface.
Source Notes
Distilled from the Codex capabilities transcript: Chronicle can provide recent screen context, but should be used with explicit intent and privacy discipline.
