Repository navigation
feat(device): add dcd device inspect, screenshot, run, logs and open - #232
Merged
Merged
Conversation
…ch and models
The first stages of the Agent Devices CLI (dcd plan 3.1 and 3.2).
- --json prints one envelope, {ok, session, data, error}, on success
and on failure.
- Exit codes: 0 ok, 1 usage, 2 failed, 3 limit, 4 session ended or
not found.
- The session id may be left out when exactly one session is open.
- start --app uploads a local build first; an https URL goes to the
API's install-from-URL.
- Progress goes to stderr, with no spinner unless at a terminal.
Hidden from dcd --help until the API reaches production.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018tQfgpTsA9UhcopKoDezUA
Stage 3.3 of the Agent Devices CLI. - inspect prints the compact screen; screenshot saves the frame to a file and reports its path. - run sends one flow (a file or --yaml) with optional --env KEY=VALUE, and polls a flow that outlasts the API's wait. A failed flow exits 2. - logs prints the app's recent log lines; --follow keeps printing new ones until the session ends. - open opens the monitor at a terminal, and prints its URL otherwise. Running a directory of flows needs an API change first and is refused for now. openBrowser moves out of login.ts so device can share it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018tQfgpTsA9UhcopKoDezUA
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
logs --follow, a long run and start --wait reused the token resolved at the start. A dcd login access token lasts about an hour, so a poll past that failed with an auth error. Each poll now calls refreshAuth first; an API key is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018tQfgpTsA9UhcopKoDezUA
Base automatically changed from
feat/device-commands
to
feature/agent-devices
October 19, 2026 11:21
…/device-inspect-run # Conflicts: # src/commands/device.ts # src/gateways/device-gateway.ts # src/types/domain/device-session.types.ts # test/unit/device-command.test.ts
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
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
1 participant
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.
Stacked on #231. Stage 3.3 of the Agent Devices CLI (dcd
docs/device-v1-plan.md).Commands
--jsongives the API's object as is../<session>-<time>.jpg) and reports the path. It never writes image bytes to stdout.--yaml.--envcan be given more than once; the API seals the values. If the flow outlasts the API's ~110s wait, the CLI polls the command until it is done. A failed flow exits 2 and still prints the output.--followpolls every 3s and prints only new lines, until the session ends. It can't be combined with--json.Not in this PR
runtakesflowUploadId, but no endpoint creates a flow upload on its own: the upload row is made only when a test run is submitted. That needs an API change first. Until then,run <dir>is refused with a clear message.logs --since(from the original spec). The API only takes a line count.Other changes
openBrowsermoves fromlogin.tstosrc/utils/browser.ts, sodevice opencan use it. citty keeps only the last value of a repeated flag, so--envis read from argv.Tests
12 more tests in
test/unit/device-command.test.ts: request bodies, the poll of a running flow, failed-flow exit code, saved screenshots, the log-overlap logic and the flag parsing.pnpm lint,pnpm typecheck,pnpm test:unit(384 passing) andpnpm buildpass.🤖 Generated with Claude Code
https://claude.ai/code/session_018tQfgpTsA9UhcopKoDezUA