Session Persistence
Medium
- Category
- Rogue Agent
- Content
2. **Verify reality**: use `opencli browser <session> state`, `find`, `network`, and `analyze`; browser state is truth. If you just completed an `opencli-adapter-author` session for this site, start from the retained browse trace under `~/.opencli/sites/<site>/traces/` as seed evidence instead of re-discovering the path from zero. 3. **Record only durable structure**: page purpose, stable anchors, state signature, actions, workflows, API references, pitfalls. 4. **Use stable ids**: page/action/workflow ids should survive URL params, locale text drift, and minor layout changes. 5. **Write local draft**: update `~/.opencli/sites/<site>/sitemap/...` unless explicitly promoting to repo. 6. **Mark stale on conflict**: if existing sitemap disagrees with current browser state, trust browser state and mark the item stale rather than forcing the old path. ---
- Confidence
- 86% confidence
- Finding
- The skill explicitly directs persistence of locally discovered site data and reuse of retained traces under `~/.opencli/sites/<site>/traces/` and `.../sitemap/`. Even though the skill says not to store secrets, session traces and local drafts can easily capture sensitive browsing context, internal URLs, identifiers, or state that later agents can access, creating cross-session data retention and unintended disclosure risk.
