NI0317
3.4 KiB
Agent Note: Web agents receive explicit runtime context
Status: implemented
English | 中文
Problem
The Web composition configured an empty deployment persona and added no launcher-owned source or interaction-surface section. A session header recorded its working directory for tools and persistence, but the model prompt did not state that directory or identify the DeepSeek Harness Web GUI. A request such as “change this page's theme” therefore made the agent search the selected project for an unspecified page, even when the user meant the GUI running the session.
Decision
The shared Web/headless composition supplies a concise coding-agent persona containing the resolved {{model}} and session {{cwd}}. dsh web additionally resolves the harness checkout from the launcher's module URL, installs the existing harness:source section, and adds an app:web-surface section before serving requests.
The Web section treats unqualified references to “this page,” “this GUI,” or “this app” as references to the DeepSeek Harness Web GUI. It also states that the browser provides no implicit DOM, route, or screenshot context, so the model can identify the product without claiming visual state it did not receive. The assembled text is logged in request/header, preserving the model-visible/logged invariant.
Verification
The keyless fresh-round-trip Web scenario boots the shipped composition, installs the same launcher context as dsh web, runs a real session through the HTTP/SSE application, and snapshots the first four system-prompt sections with source and working-directory paths normalized. The snapshot pins the harness identity, source checkout, Web orientation, and resolved coding-agent persona in request order.
Alternatives considered
Send URL, DOM, or screenshots with every prompt. The observed failure needed stable product orientation, while the current root URL does not identify a selected component and no visual capture exists in the message contract. Adding dynamic page state would require a separate logged model-input design and is not implied by this fix.
Require the session Workspace to be the harness checkout. Workspace cwd is the user's task target and may legitimately be an empty project or another repository. Conflating it with the application's source location would break that boundary and leave installed or externally launched sessions ambiguous.
Put Web wording in the global harness identity. dsh-system-prompt serves TUI, ACP, SDK, and custom deployments that do not run in a browser. The composing Web app owns this surface fact.
Change the existing source-location section for every CLI surface. The source section is shared with TUI and states only the checkout fact. Keeping Web orientation separate preserves that reusable contract and avoids telling headless or terminal agents that they are in a browser.
Consequences
Web requests gain a short stable prompt prefix and may invalidate provider prefix caches once when this change is deployed. Agents can distinguish the GUI source checkout from the selected Workspace and resolve ordinary references to the current app without a clarification round trip. References to a specific visual state remain bounded by the explicit no-DOM/no-route/no-screenshot statement and may still require a path, description, or attachment.