Skip to content

feat(facade): re-export carried-coreutils dispatch API + bump 0.7.1#213

Merged
hartsock merged 1 commit into
mainfrom
feat/facade-coreutils-dispatch
Jul 6, 2026
Merged

feat(facade): re-export carried-coreutils dispatch API + bump 0.7.1#213
hartsock merged 1 commit into
mainfrom
feat/facade-coreutils-dispatch

Conversation

@hartsock

@hartsock hartsock commented Jul 6, 2026

Copy link
Copy Markdown
Member

Re-exports maybe_dispatch/register_shims/install_default_providers from the agent-bridle facade under carried-coreutils (the 0.7.0 facade only had them on agent-bridle-tool-shell). Lets a host binary call agent_bridle::maybe_dispatch() in main to enable carried coreutils (newt follow-up). Bumps 0.7.0 → 0.7.1. risk:low.

The 0.7.0 facade exported `BrushShellTool` but not the dispatch entry points, so
an embedder had to depend on `agent-bridle-tool-shell` directly to make its
binary dispatch-capable. Re-export `maybe_dispatch` / `register_shims` /
`install_default_providers` from the facade under `carried-coreutils`, so a host
(newt) can call `agent_bridle::maybe_dispatch()` at the top of `main` and turn on
carried coreutils. Version metadata only otherwise; bump 0.7.0 → 0.7.1.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HRv5vteHCw4jUayHGL5esx
@hartsock hartsock merged commit f19ec0a into main Jul 6, 2026
10 checks passed
@hartsock hartsock deleted the feat/facade-coreutils-dispatch branch July 6, 2026 21:30
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.

1 participant