feat(composer): re-export canonical AgentComposer from sandbox-ui#156
Merged
Conversation
Add an opt-in `@tangle-network/agent-app/composer` entry that re-exports the canonical AgentComposer + AgentProfilePicker (and the session-control / reasoning / snapping kit) from @tangle-network/sandbox-ui, so agent-app apps adopt the one shared chat input box without each wiring sandbox-ui directly. New UI should prefer this over the legacy web-react composer. Additive and blast-radius-minimal: a dedicated subpath, so sandbox-ui stays an optional peer for everyone else; the existing web-react composer is untouched. Bump the sandbox-ui floor ^0.44 → ^0.59 (dep + peer) for AgentComposer. ESM + DTS build green; the composer entry emits and re-exports AgentComposer.
tangletools
approved these changes
Jun 30, 2026
tangletools
left a comment
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved drewstone PR — c7604590
This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
tangletools · auto-approval · reason: drewstone_author · 2026-06-30T00:21:36Z
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
2 participants
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.
Problem
agent-app ships its own
chat-composer/agent-session-controls/provider-logoinweb-react, which duplicate@tangle-network/sandbox-ui. Apps wanting the canonical, best-in-class composer had to wire sandbox-ui themselves.Change
Add an opt-in
@tangle-network/agent-app/composerentry that re-exports the canonicalAgentComposer+AgentProfilePicker(plus the session-control, reasoning, and harness↔model snapping kit, and theModelInfo/HarnessTypetypes) from sandbox-ui. New UI should prefer this over the legacyweb-reactcomposer.@tangle-network/sandbox-uistays an optional peer for every other consumer — only code importing/composerpulls it. The existingweb-reactcomposer is untouched (no breaking changes).^0.44→^0.59(dep + peer) soAgentComposerresolves.Why
This is the last leg of unifying the chat composer across the stack: sandbox-ui owns the one design (0.59), the sandbox marketing hero and tuner-agent now consume it, and this exposes it through the substrate every agent-app app already depends on. Follow-up (separate, higher-blast-radius): migrate agent-app's own
web-reactcomposer to delegate toAgentComposerand retire the duplicate.Tests / proof
dist/composer/index.{js,d.ts}emit and re-exportAgentComposer.