feat(wallet): add remote-host handoff for wallet login and funding#388
Conversation
Slokh
left a comment
There was a problem hiding this comment.
thanks for this, few comments
|
@pejmanjohn can you lint / fmt / add changelog entry, thanks! lgtm to merge otherwise |
|
@Slokh hopefully this addresses everything - if not lmk! Pushed |
|
@pejmanjohn Looks good, I'll merge and do a 0.2.2 release for you, since we don't have any plans for changes in the next week. |
This adds an explicit remote-host path for
tempo wallet loginandtempo wallet fundvia--no-browser, plus the CLI, skill, and README guidance that remote agents need to hand the flow off to a user on another device.OpenClaw-style agents run the CLI on one host while the human approves wallet actions from another device. Today the CLI already prints the auth URL/code, but the flow still defaults to opening a browser on the host and the narration stays same-machine oriented. This change makes that remote handoff a supported path without regressing the default local browser flow.
What changed:
--no-browsertotempo wallet loginandtempo wallet fundSKILL.md,README.md, andcrates/tempo-wallet/README.mdThis improves the CLI contract for remote-host agents, but it does not change wallet/auth backend semantics. If wallet creation still requires a second authorization round before the host is fully authorized, that follow-up still needs to be fixed outside this repo.
Verification:
cargo fmt --all --checkcargo clippy --workspace --all-targets --all-features --locked -- -D warningscargo run -p tempo-wallet -- login --helpcargo run -p tempo-wallet -- fund --helpcargo test -p tempo-wallet --test remote_flows -- --nocaptureRUSTDOCFLAGS='-D warnings' cargo doc --workspace --all-features --no-deps --lockedcargo test --workspace --all-features --lockedis flaky locally becausepayment::session::streaming::tests::submit_voucher_update_caches_head_unsupported_per_originintempo-requestintermittently fails in the full suite while isolated reruns pass