Skip to content

feat(protocol): typed daemon event schema v1 #4217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wenshao merged 1 commit into from
May 17, 2026
Merged

feat(protocol): typed daemon event schema v1 #4217

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions packages/sdk-typescript/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,28 @@ reported on the create/attach HTTP response. Raw `DaemonClient` callers should
pass `{ lastEventId: 0 }` on their first `subscribeEvents()` call when they use
`modelServiceId`.

The raw event envelope remains available as `DaemonEvent` with `data: unknown`.
Adapters that want a v1 typed view can layer the schema helpers on top without
changing the wire stream:

```typescript
import {
asKnownDaemonEvent,
createDaemonSessionViewState,
reduceDaemonSessionEvent,
} from '@qwen-code/sdk';

let view = createDaemonSessionViewState();
for await (const event of session.events()) {
view = reduceDaemonSessionEvent(view, event);

const known = asKnownDaemonEvent(event);
Comment thread
chiga0 marked this conversation as resolved.
if (known?.type === 'permission_request') {
console.log(known.data.requestId);
}
}
```

### Message Types

The SDK provides type guards to identify different message types:
Expand Down
Loading
Loading