Skip to content

Don't install Databricks AI Tools on agent launch (configure-only) - #350

Merged
rohita5l merged 3 commits into
mainfrom
no-skills-install-on-launch
Aug 17, 2026
Merged

Don't install Databricks AI Tools on agent launch (configure-only)#350
rohita5l merged 3 commits into
mainfrom
no-skills-install-on-launch

Conversation

@rohita5l

Copy link
Copy Markdown
Collaborator

Problem

Running a launch command like:

ucode claude --provider main.jasmine.rohit-test --workspace https://<ws>

prints "Installing Databricks AI Tools for claude-code..." unprompted. Launch commands auto-configure an unseen agent through configure_single_tool, which also installed Databricks AI Tools (skills + plugins). That put skill installation on the launch path, not just the configure path.

Fix

Move the install out of the shared configure_single_tool and into the ucode configure callers only:

  • configure_single_tool no longer installs — the launch path (_auto_configure_tool) auto-configures through it and must never install skills.
  • configure_workspace_command installs explicitly after configure_single_tool on the single-agent path; the multi-agent path already installs via configure_selected_tools.

Result

  • Launch (ucode claude, etc.) never installs skills. ucode claude --provider ... --workspace ... now just configures the agent for the provider and launches — no install step.
  • ucode configure still installs, on by default, with --disable-databricks-ai-tools to opt out (unchanged).

Testing

  • TestConfigureWiresAiToolsInstall: configure_single_tool is now asserted to not install; configure_selected_tools still does.
  • The configure single-agent cli test now asserts the configure path installs (and mocks it, so it no longer makes a real databricks aitools subprocess call).
  • tests/test_agents_init.py + tests/test_cli.py: 288 passed. Lint + format clean.

This pull request and its description were written by Isaac.

`ucode claude` (and the other launch commands) auto-configure an unseen agent
via configure_single_tool, which also installed Databricks AI Tools (skills +
plugins). That put skill installation on the launch path, so a plain
`ucode claude --provider ... --workspace ...` printed "Installing Databricks AI
Tools for claude-code..." unprompted.

Move the install out of the shared configure_single_tool and into the
`ucode configure` callers only:
- configure_single_tool no longer installs (launch auto-configures through it).
- configure_workspace_command installs explicitly after it (single-agent path);
  the multi-agent path already installs via configure_selected_tools.

Result: launch never installs skills; `ucode configure` still does (default on,
`--disable-databricks-ai-tools` to opt out).

Co-authored-by: Isaac
@rohita5l
rohita5l requested a review from lilly-luo August 17, 2026 23:29
Comment thread src/ucode/cli.py Outdated
Comment thread src/ucode/agents/__init__.py Outdated
…_agents

Clarify (per review) that these are Databricks' AI Tools, not the customer's.

Co-authored-by: Isaac
Comment thread src/ucode/cli.py Outdated
@rohita5l
rohita5l enabled auto-merge (squash) August 17, 2026 23:46
@rohita5l
rohita5l merged commit 8bc9c9e into main Aug 17, 2026
2 checks passed
@rohita5l
rohita5l deleted the no-skills-install-on-launch branch August 17, 2026 23:50
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.

2 participants