You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stacked on #381 and addresses the CLI UX direction tracked in #384.
Moves Obol-owned lifecycle/auth/wallet/list/delete/sync/setup/new commands under obol agent.
Changes obol hermes into native Hermes CLI passthrough, with --agent <id> for non-default Hermes instances and obol-agent as the default target when present.
Keeps obol openclaw as the manual OpenClaw runtime path while adding obol agent --runtime openclaw management coverage.
Updates docs, smoke flows, and helper messages away from removed Hermes lifecycle commands.
Testing coverage follow-up from the subagent review is now pushed in ac952d1.
Added:
Table-driven coverage for resolveAgentTarget and resolveRuntimeInstance, including default Hermes preference, explicit runtime selection, unknown instances, ambiguous IDs across runtimes, and multi-instance errors.
Table-driven coverage for ResolveCLIInvocation, including --agent=value, -- passthrough, missing/duplicate --agent, unknown agents, no instances, single-instance fallback, and multiple non-default instances.
Flow 04 smoke step for native Hermes CLI passthrough via obol hermes --agent obol-agent version.
Validation after the update:
go test ./cmd/obol ./internal/hermes ./internal/agentruntime ./internal/stack ./internal/tunnel
Function coverage for the risky new routing helpers is now high: resolveAgentTarget 90%, resolveRuntimeInstance 92.9%, ResolveCLIInvocation 94.1%, splitCLISelection 87.5%.
Rebased onto current main (post-#386 squash merge).
Before: 13 commits on top of main, 21-file conflict — most of those commits (e5fe270…9f8b7ff, the Hermes runtime work) had already landed in main via squash f08651e, but git still saw them as ahead.
After: 2 unique commits remain — Move agent lifecycle UX under obol agent + Add agent CLI resolver coverage. Cherry-picked cleanly with three small conflict resolutions:
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
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
Stacked on #381 and addresses the CLI UX direction tracked in #384.
obol agent.obol hermesinto native Hermes CLI passthrough, with--agent <id>for non-default Hermes instances andobol-agentas the default target when present.obol openclawas the manual OpenClaw runtime path while addingobol agent --runtime openclawmanagement coverage.Validation
go test ./cmd/obolgo test ./internal/hermes ./internal/agentruntimego test ./internal/stack ./internal/tunnelgo test ./...go build -o .workspace/bin/obol ./cmd/obolbash -n flows/flow-04-agent.sh flows/flow-11-dual-stack.sh