Yichen Jiang
8f3103b511
- session.killJob maps job-not-found from the lookup only: jobs.get gates the same synchronous span, so a producer-cancel throw now propagates per the registry contract (job state unchanged) instead of masquerading as a lookup failure (threads r3860226021, r3860226047). - session.killJob applies the service-wide subagent ownership fence exactly as cancel does; a subagent-owned live session rejects with the ownership error and the child-owned job stays running (thread r3860226041). - The stop control stays pending on an admitted kill: the unary response and the jobs frames have no cross-carrier ordering, so only the authoritative frame (the row leaving the killable set) releases the button, closing the duplicate-kill window (thread r3860226028). - One-line comment on the killReason assignment stating last-writer-wins is intended, beside the first-claim-wins reported handling (thread r3860225999). Host spec pins the producer-throw propagation and the fence; the component spec pins pending-until-frame; the Agent Note records both refinements.
description, kind
| description | kind |
|---|---|
| Package map for the application's Remote layer: typed Client-to-Host capability calls, results, and forwarded events, for users and maintainers navigating the group. | package-group |
api/ — Remote API layers
English | 中文
Summary
The api/ group provides the application's Remote layer: a Client environment can call the business capabilities running on the Host — manage goals, run commands, list the plugin inventory, discover file and session references — as typed method calls, and receive the results or forwarded Host events. remotes decides which capabilities are exposed and how each call reaches the right session's agent; gateway carries the calls and their results between Client and Host. The stack runs over the application's shared Connection; streaming session data is deliberately outside it.
Table of Contents
Packages
The packages below provide the Remote layer; the package READMEs own the exhaustive contracts.
| Package | Role | ctx key |
|---|---|---|
remotes/ |
Chooses which Host capabilities and events the Client can consume. | — |
gateway/ |
Carries typed unary calls, multiplexed streams, and forwarded Host events. | ctx.typertGateway / ctx.remote |
session-controller/ |
Owns Session commands, history streams, live control state, and Agent/Session identity policy. | ctx.sessionController / ctx.remote.session |
workspace-controller/ |
Owns Workspace mutations and the complete Client Workspace projection. | ctx.workspaceController / ctx.remote.workspace |
Remote calls run Client → Host over the application's shared Connection. API Gateway owns Remote transport, while the two controller packages own Session and Workspace behavior. Endpoints without a Remote definition fall through to the application's API Proxy.
Related documentation
Start with the API Gateway reference to see the Remote model end to end, then the Typert subsystem page for the shared definitions, and the carrier and fallback packages for how calls travel and how endpoints without Remote definitions are served.
- API Gateway reference — the current-state reference for the Typert API Gateway: programming model, generation pipeline, and runtime invocation.
- Typert subsystem reference — the public contracts shared by protocol, Gateway, and consumer assemblies.
- Connection — the RPC carrier,
/apitrust fence, and response envelopes behind every Remote call. - API Proxy — the fallback for endpoints without Remote descriptors.
Dev Note
Working context for maintainers — click to expand
None.