Repository navigation
docs: document Attention API and shared chat policy - #43
Merged
Merged
Conversation
…very - Action tools take a `targets` array whose items are the `action_ref` or `target_ref` objects copied verbatim; list all nine read tools, `attention_context_set` and the four action tools with their arguments, including the visual capture options. - State that `attention_inspect` was removed. - Document every terminal action status, the envelope limits for wippy.attention v1 to v4 and wippy.attention.visual v1, and the GET /api/v1/sessions/capabilities descriptor. - Describe plain-message delivery with the tab binding, read withdrawal, guard refusals, per-Session automatic context, upload listing, approved image delivery, composer exclusion, turn errors, and the PNG/WebP upload type requirement for visual capture. - Replace the debugging note with checks for Host config, Session capabilities and the agent trait, and remove internal process text.
- check-attention-context-docs.mjs now requires the `targets` array wording, the removed `attention_inspect` wording, the complete tool list, every terminal status, per-version envelope limits and the capability descriptor fields, and rejects the old `target_ref` wording and internal process text. - Add a Documentation checks workflow that runs the frontend, Attention and Markdown link checkers on pull requests and pushes to main. - Document the Attention checker in the README.
The pages said the agent can turn automatic pointing context on or off without asking the user. That is true of the tool, but the Attention trait tells the model to use it only when the user asks. State both, so readers do not assume the agent changes the setting on its own initiative.
wolfy-j
changed the title
wolfy-j
marked this pull request as ready for review
October 31, 2026 13:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document the Attention inspection API, its agent trait and 14 tools, Session context controls, immutable action targets, approved capture drafts, delivery and privacy. Add a quickstart in eight locales and document shared chat policy.
The guidance targets published Host 1.0.67, proxy/shared 0.0.67, Facade 0.6.49, Session 0.6.17 and Agent 0.5.9. Current schema 2.2, import-map bootstrap ordering, Iconify and self-hosting guidance are preserved. The fixture checker validates structured JSON rather than freezing prose wording.
Validation:
Browser proof uses current app source 31287ff, official Runtime v0.3.56a, and published modules only (also LLM 0.5.12, Relay 0.3.20, Views 0.5.13). No local Host assets or module replacements. This is focused Chromium qualification, not a full platform suite or Firefox/WebKit claim. Deployment-specific capture, privacy and authorization checks remain documented.