You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a daemon-owned events.ndjson timeline under each session state dir so EAS and local tooling can show what the agent did during a run.
Record request start/finish entries and recorded actions, with sensitive typed text redacted while keeping target/ref/coordinate and duration context.
Expose the timeline through agent-device events, the typed observability client, and open-result eventLogPath for direct VM/local file collection.
Validation
Verified with focused daemon/session-store/observability/CLI/remote-daemon tests, pnpm typecheck, pnpm format, pnpm build, and pnpm check:unit outside the sandbox. Unit + smoke passed: 2,979 unit tests and 9 smoke tests; the live web smoke stayed skipped because AGENT_DEVICE_WEB_E2E was not set.
Touched-file count: 23. Scope stayed within session event logging, observability command surface, client/open result plumbing, and remote RPC coverage.
I found one issue that should be fixed before this merges:
The event timeline still leaks raw payload-bearing positionals for commands outside the current type/fill/find special cases. buildDisplayPositionals in src/daemon/session-event-action.ts falls back to action.positionals for most commands, so session-recorded actions like clipboard write <secret> from src/daemon/handlers/session.ts and inline push <app> <payload-json> from the same handler can persist the raw secret/payload into events.ndjson.
That matters more now because this PR exposes eventLogPath for collection by local/EAS tooling. The fix should centralize display-positionals redaction for every command that carries user text or inline payloads, not just typed input. The rest of the architecture looks like a good fit: session-owned timeline, observability command exposure, and request start/finish recording at the request-scope/finalization layer.
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
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.
Summary
events.ndjsontimeline under each session state dir so EAS and local tooling can show what the agent did during a run.agent-device events, the typed observability client, and open-resulteventLogPathfor direct VM/local file collection.Validation
Verified with focused daemon/session-store/observability/CLI/remote-daemon tests,
pnpm typecheck,pnpm format,pnpm build, andpnpm check:unitoutside the sandbox. Unit + smoke passed: 2,979 unit tests and 9 smoke tests; the live web smoke stayed skipped becauseAGENT_DEVICE_WEB_E2Ewas not set.Touched-file count: 23. Scope stayed within session event logging, observability command surface, client/open result plumbing, and remote RPC coverage.