Add local IPC API and resilient API client - #196
Open
Tylerpro09 wants to merge 2 commits into
Open
Conversation
…ogic Add local IPC API and resilient API client
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
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.
What changed
docs/ipc-api.md.Why
Automation, dashboards, and MCP-style integrations need a stable local control surface without exposing the agent secret. The API client also needs to tolerate transient network failures and report non-successful API responses clearly.
Impact
Local clients can query status and tunnels, create or delete tunnels, inspect account state, and start claim provisioning over the existing local IPC transport. Unix socket permissions and the restricted Windows named-pipe ACL remain the access-control boundary.
Validation
cargo fmt --checkcargo check --workspacecargo test --workspace --no-fail-fast