ai: blocktank lsp api plugin + agent control interface#860
Open
ai: blocktank lsp api plugin + agent control interface#860
Conversation
916f93c to
c3fc52e
Compare
142abce to
eb2fe0d
Compare
66285e8 to
2e069ad
Compare
.claude/plugins/blocktank-api/skills/lsp/scripts/pay-invoices.sh
Outdated
Show resolved
Hide resolved
This comment has been minimized.
This comment has been minimized.
Member
|
@claude explain me from this PR how the agent can communicate with the app |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
jvsena42
reviewed
Mar 26, 2026
This comment has been minimized.
This comment has been minimized.
jvsena42
reviewed
Mar 27, 2026
Member
jvsena42
left a comment
There was a problem hiding this comment.
the terminal commands worked but the the Claude didn't. I'm investigating
❯ pay 4 invoices of 100 sats using lsp skill
⏺ Skill(lsp)
⎿ Initializing…
⎿ Error: Unknown skill: lsp
⏺ There is no "lsp" skill available. The available skills are:
- /pr — Create a PR on GitHub
- /release — Create a new release
- /simplify — Review changed code for quality
- /loop — Run a command on a recurring interval
- /schedule — Manage scheduled remote agents
- /claude-api — Build apps with Claude API
- /update-config — Configure Claude Code settings
- /keybindings-help — Customize keyboard shortcuts
- /plannotator-review — Interactive code review
- /plannotator-annotate — Annotate markdown files
- /plannotator-last — Annotate last assistant message
- /plannotator-archive — Browse saved plan decisions
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.
This PR:
./lspCLI wrapper for calling the Blocktank API from the repo rootDevToolsProviderContentProvider (debug builds only) for programmatic invoice creation viaadb shell content callpay-invoices.shautomation script for bulk invoice creation, payment, and block miningDescription
Blocktank LSP API Plugin for Claude Code - 142abce
Introduces a Claude Code plugin at
.claude/plugins/blocktank-api/that gives Claude knowledge of the Blocktank LSP REST API (18 endpoints) and provides shell scripts for calling it. The plugin includes a skill with endpoint tables, common workflows (channel purchase, CJIT, force close), and state machine documentation.Agent Control Interface (ACI) - 142abce
A debug-only
DevToolsProviderContentProvider allows creating bolt11 invoices on the app's LDK node viaadb shell content call, returning the result synchronously as JSON in a Bundle. Commands accept typed JSON args via--arg, with each command defining its own@Serializabledata class for type-safe deserialization with defaults.This MVP provides the basis for demonstrating 2-way communication between AI dev agents and the Bitkit Android App. Future implementations could expand the set of supported methods through this command interface, as the internals of the implementation were designed with extensibility in mind.
A potential 2nd layer could provide agent-to-app control by deep-linking directly to different routes within the app, optionally passing args to fill-in screen details such as route params or values for form inputs.
Preview
lsp_1.5x.mp4
QA Notes
1. Verify
./lspwrapper2. Verify invoice creation via claude code
prerequisite: debug build with wallet + open channel actively running on emulator
3. Verify full automation
prerequisite: open channel with inbound capacity