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.
Been playing with the new DuckDB UI stuff and Claude Code a lot this week and cooked up something simple that does what I've always wanted to be able to do with dbt and DuckDB: run the dbt-duckdb process in a shell process where I could simultaneously query the DuckDB instance via a UI and run my dbt-duckdb models in a high-fidelity way, with all of the python model execution and all of the other great stuff we've built in this project over the last few years.
The idea is to create a
cli.py
and a newduckdbt
shell command that uses the dbtRunner construct to load up dbt, parse all of the models in a project using a given profile, and let you run command invocations in the CLI while simultaneously launching the DuckDB UI via aCALL start_ui()
call against the instance of DuckDB that gets loaded and configured whendbt debug
is called.