高风险
已登录页面的完整 API 响应会写入持久网络缓存
原文依据：3 处发现了什么
Skill 优先建议捕获网络数据，支持输出单个或全部完整响应正文，并将缓存保存在 `~/.opencli/cache/browser-network/`，默认 TTL 为 24 小时。响应可能包含个人资料、消息、会话令牌或业务数据。
为什么需要注意
敏感响应可能同时出现在代理输出和本地缓存中，之后被其他进程、备份或后续会话读取。
该 Skill 建议优先捕获页面 API，并允许读取单个或全部完整响应正文；捕获内容会缓存在用户主目录下，默认 TTL 为 24 小时。若在已登录标签页中使用，正文可能含账户或业务数据。源码没有证明一定含会话令牌，也没有说明缓存的权限、加密或清理方式，但持久保存敏感响应是可信风险。用户可限制 `network --raw`、缩短 TTL，并要求说明缓存保护和删除机制。
9. **`eval` is read-only.** Wrap the JS in an IIFE and return JSON. If you need to *change* the page, use the structured `click` / `type` / `select` / `keys` commands instead — they produce structured output and fingerprints, `eval` does not.10. **Prefer `network` to screen-scraping.** If a page you care about fetches its data from a JSON API, the API is almost always more reliable than scraping the rendered DOM. Capture once, inspect the shape, then `--detail <key>` the body you need.查看另外 2 个位置
```bashbrowser network # shape preview + cache key listbrowser network --detail <key> # full body for one cached entrybrowser network --filter "field1,field2" # keep only entries whose body shape contains ALL fields as path segmentsbrowser network --all # include static resources (usually noise)browser network --raw # full bodies inline — large; use sparinglybrowser network --ttl <ms> # cache TTL (default 24h)```List entries look like `{key, method, status, url, ct, size, shape, body_truncated?}`. Detail envelope is `{key, url, method, status, ct, size, shape, body, body_truncated?, body_full_size?, body_truncation_reason}`. Cache lives in `~/.opencli/cache/browser-network/` so you can re-inspect without re-triggering the request.List entries look like `{key, method, status, url, ct, size, shape, body_truncated?}`. Detail envelope is `{key, url, method, status, ct, size, shape, body, body_truncated?, body_full_size?, body_truncation_reason}`. Cache lives in `~/.opencli/cache/browser-network/` so you can re-inspect without re-triggering the request.