Skip to content

Add Muse Code harness support - #105

Merged
JacobStephens2 merged 1 commit into
mainfrom
feat/muse-harness
Sep 13, 2026
Merged

JacobStephens2 merged 1 commit into
mainfrom
feat/muse-harness

Conversation

@JacobStephens2

Copy link
Copy Markdown
Owner

Adds Muse Code as a standard Harness so va muse launches with the selected Manifest and va muse --yolo forwards Muse's native flag unchanged. The default is bare muse in the caller's directory, preserving Muse's permission settings and native resume arguments.

Includes the shipped profile, installer discovery and existing-profile preservation, Doctor working-directory checks, operator documentation, and CLI acceptance tests. Uses the existing secret-resolution and Manager-token removal path.

Closes #103.

Validation:

  • cargo test
  • cargo check --all-targets
  • cargo fmt --check
  • cargo clippy --all-targets -- -D warnings
  • bash -n install.sh
  • A real Muse 1.1.1 shell launched through the built Launcher with exec --yolo received an injected non-secret sentinel; the tool result reported the expected output and exit code 0. No real third-party credential or authenticated external action was tested.

Standards and Spec reviews completed: no correctness or spec findings; one optional note about the installer's existing repeated discovery pattern was left for a broader refactor.

@JacobStephens2
JacobStephens2 merged commit fee4b06 into main Sep 13, 2026
2 checks passed
@JacobStephens2
JacobStephens2 deleted the feat/muse-harness branch September 13, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

as a muse code user, i want to inject secrets into my agent session so I can have muse code do authenticated actions

1 participant