You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2bd6632
Browse filesBrowse the repository at this point in the historyBrowse files
feat(workspace): tell the model about extension tools a live IDE bridge serves (#1291)
* feat(workspace): tell the model about extension tools a live IDE bridge serves
The `## Workspace integrations` section projected only the three warehouse
capabilities per connection type, so extension-type tools the engine serves
through a live VS Code bridge (the dbt project tools, sql-tools) never
reached the model even when they sat in its catalog. The presentation
surfaces learned about them in #1236; this is the model-facing half.
- `declared()` groups the extension keys under their catalog integration
(`Declared.extensions`, optional so the flat lists stay the contract),
and the attach outcome carries the groups so precedence never makes a
second lookup.
- `derive` names an extension tool only when two signals agree: its key
materialised in the live catalog AND a bridge for this project is live
now. Either missing is silence, not a warning. The tools ride on the
`nothing-materialised` snapshot too, since a workspace can serve
extension tools and no warehouse capability at all.
- `servedExtensions` applies the same reachability filter as the warehouse
inventory, at projection time, so an `analyst` is never told about tools
it may not call.
- The section appends the groups under a fixed intro naming the condition
they depend on; a workspace with extension tools and nothing routed gets
an extension-only shape that keeps the local-tools sentence. Extension
lines are dropped before any warehouse type when the cap is hit.
Every snapshot without extension tools renders byte-for-byte what it did
before, including all silent disabled states.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GHBUvb843k1R7UAGi8Ya9b
* fix(workspace): a claim about this project's bridge needs a verified pid, not a pidless sidecar
liveBridge's option is now { claim }: for the prompt's sentence about the window open on this project, a recorded folder match on a sidecar whose pid is verified alive, or nothing. The sole-bridge fallback and the pidless-sidecar tolerance stay for the attach path, which mirrors the engine's own discovery.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GHBUvb843k1R7UAGi8Ya9b
* fix(workspace): the live-bridge seam carries the claim option through
So a test that stands in for the sidecar read sees whether the caller asked for a claim.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GHBUvb843k1R7UAGi8Ya9b
* test(workspace): pin that the bridge probe is asked as a claim through the seam
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GHBUvb843k1R7UAGi8Ya9b
---------
Co-authored-by: ralphstodomingo <[email protected]>
Co-authored-by: Claude Fable 5.1 <[email protected]>
0 commit comments