feat: expose apps list in node client#378
Merged
Merged
Conversation
thymikee
force-pushed
the
codex/expose-apps-list-node-api
branch
from
5d39c0c to
9d8f110
Compare
|
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.
Summary
Expose
client.apps.list(options?)on the Node API and forwardappsFilterto the existing daemonappscommand.Return the current daemon
data.appsstring list and add createAgentDeviceClient coverage for filter forwarding. Updated the typed client docs. Touched 8 files; scope stayed within the Node client/API test surface plus docs/stub updates.Validation
pnpm install --frozen-lockfilepnpm formatpnpm typecheckpnpm check:unitgit diff --checkKnown gaps: none.