Repository navigation
Conversation
When OmniSynth (omniaura/omnisynth) runs on this machine it writes a loopback discovery file with a port and bearer token. This adds an OmniSynthService that reads it at call time and an `omnisynth` MCP toolkit — omnisynth_status, omnisynth_generate, omnisynth_tool, omnisynth_state, omnisynth_launch — so an agent in any thread can build or evolve music the user hears immediately. Access is a new server-authoritative, project-overridable setting (enableAgentOmniSynthAccess, off by default) that grants the `omnisynth` MCP capability the way device access grants `device`. Codex gets an instruction block only when the toolkit is attached. Settings → Integrations gains an OmniSynth section; docs/user/omnisynth.md explains what "works together" means. Verified: contracts/server/web typecheck clean for touched files; new handlers test (5) and neighbouring MCP/Codex/settings tests pass; the service was driven live against a running OmniSynth (status → 35 tools, set_bpm, state, error surfacing). Model: Claude Fable 5.1 via Claude Code. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
Thread transfer impact
This comment will update automatically after the next completed run. |
This branch has not been deployed
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.
What Changed
Adds an OmniSynth integration: when OmniSynth (the open-source LLM-native DAW) is open on the environment's machine, every agent session gets
omnisynth_*tools on thet3-codeMCP server.apps/server/src/omnisynth/OmniSynthService.ts— reads OmniSynth's loopback discovery file (~/Library/Application Support/OmniSynth/bridge.json: port + per-launch bearer token) at call time;/healthfailing on a stale file means "installed, not running".launchopens the app via the OS (omnisynth://generate?prompt=…when a prompt is given) and waits for the bridge.apps/server/src/mcp/toolkits/omnisynth/{tools,handlers}.ts—omnisynth_status(installed/running/song + the DAW tool catalog + just-in-time quick start),omnisynth_generate(whole-song Perceive→Orchestrate run, taggedditto-desktop:<threadId>),omnisynth_tool(proxy any DAW tool by name),omnisynth_state,omnisynth_launch. Deliberately small: the DAW's own catalog is read live, not duplicated.omnisynthMCP capability granted byenableAgentOmniSynthAccess— server-authoritative, project-overridable, off by default, exactly likeenableAgentDeviceAccess. Settings → Integrations gains an OmniSynth section (searchable).packages/contracts/src/omnisynth.ts,docs/user/omnisynth.md(what "works together" means for users), docs index.Why
OmniSynth and Ditto Desktop are both open source and both signed into the same Ditto account; the natural seam is "the agent you already chat with can produce music you hear immediately". OmniSynth's side (bridge server, shared sign-in, credit-aware budget) is omniaura/omnisynth#3. Tracked in Jira SYNTH-44 / SYNTH-47 / SYNTH-48.
Verification
vp run typecheckinpackages/contracts,apps/server,apps/web: no new errors in touched files (pre-existingbin.test.tsnoise unchanged).vp test run src/mcp/toolkits/omnisynth/handlers.test.ts— 5 pass;McpInvocationContext,McpHttpServer,CodexDeveloperInstructions,settingsSearch,scopedSettings,ProviderService"agent browser access" tests pass.OmniSynthServicelive against a running OmniSynth: status → 35 tools,set_bpm→ "BPM 131.", state read back, bad-instrument error surfaced asOmniSynthRequestError.Checklist
Model: Claude Fable 5.1 via Claude Code.
🤖 Generated with Claude Code