Repository navigation
feat(cli): apply an Outfit before launching from outfit harness - #17
Merged
Merged
Conversation
`outfit harness` gains --outfit/-O: the Outfit to apply before the harness launches, doing the same work `outfit apply` does. Given bare it takes ./Outfit, as every other Outfit-reading command does; a path is attached to the flag (--outfit=<path>) because positional args belong to the harness, and a detached path is caught rather than silently forwarded. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012kCUwjoT8Pi8dyYMyPnSsZ
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.
outfit harnesscan now take an Outfit and apply it on the way in, so one command dresses the agent and launches it.Summary
--outfit/-Otooutfit harness: the Outfit to apply before the harness launches, doing the same workoutfit applydoes (it routes through the sameapplySelection)../Outfit— the same default asapply,unapplyandserve. A named path is attached to the flag (--outfit=PATH), and a directory holding anOutfitworks as it does elsewhere.--providerstoharnessso the pre-launch apply can resolve against a custom catalogue, asapplycan.--get/--setstay inspection/config only and apply nothing.readOutfit's not-found hint now takes the caller's own usage string, soharnesssuggestsoutfit harness --outfit=FILErather than a positional form that would not work for it.README.md,docs/outfit-file.mdandAGENTS.md.Implementation details
The flag's value is optional (
outfitPathFlagimplementsIsBoolFlag) so that a bare--outfitcan mean the default Outfit, matching every other Outfit-reading command. The consequence is that a path must be attached with=, because everything positional after the flags is forwarded to the harness —outfit harness -O run --model xstill passesrun --model xon to the agent.That leaves one trap worth guarding:
--outfit ./some/Outfitwould apply the default./Outfitand quietly hand the path to the agent. When the flag is given bare and the next positional names an Outfit file (or a directory holding one), the command errors with the attached form instead of guessing.