chore: remove the experimental Bossman harness - #443
Merged
Conversation
Bossman was an off-by-default Claude-Agent-SDK harness spike. Removes it end-to-end: - runtime: the harness-host runner + its contract type/decoder, the harnesses definition, the registry entries (harness-host + api-server), and the registry-test entry. - desktop: harness picker/avatar wiring, the Hola-model-catalog conditions (ChatPane / ProjectLanding), the experimental toggle (atom + Settings), and the sunglasses asset + its assetPaths entry. - docs: the spike plan. DEFAULT_HARNESS_ID stays pi; a legacy `run-bossman` invocation falls back to pi (requireHarnessHostPluginByCommand + its test). Typecheck green for desktop + runtime; harness-registry test passes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Removes the off-by-default Bossman harness (a Claude-Agent-SDK spike) end-to-end.
What's removed
harness-host/src/bossman.ts(host runner) +bossman.test.tsharnesses/src/bossman.ts(harness definition)HarnessHostBossmanRequesttype + decoder inharness-host/src/contracts.tsharness-host/src/harness-registry.tsandapi-server/src/harness-registry.ts(+ theharness-registry.test.tsassertion)bossmanHarnessDefinitionexport/import/registration inharnesses/src/index.tsHarnessAvatar.tsx, theHarnessPickercomment, and the now-trivial filter machinery inuseAvailableHarnesses(it existed only to hide bossman)harnessUsesHolaModelCatalogconditions inChatPaneandProjectLanding(pi only now)bossmanExperimentalEnabledAtom(shell/state/ui.ts) + the "Bossman agent" row in Settings → Appbossman-sunglasses.svgasset + itsassetPaths.tsentrydocs/plans/2026-07-03-bossman-agent-sdk-harness-spike.mdSafety
DEFAULT_HARNESS_IDstayspi.run-bossmaninvocation falls back to pi — covered byrequireHarnessHostPluginByCommandand its existing test ("falls back to pi for unregistered commands").Testing
turbo run typecheckgreen forholaboss-localand the runtime packages (harnesses,harness-host,api-server).harness-registry.test.ts: 3/3 pass.bossmanreferences inruntime/orapps/.Net: 18 files, −832 / +19.
🤖 Generated with Claude Code