Skip to content

aitools: skip the install hint on auth, lookup, and completion commands - #7452

Merged
renaudhartert-db merged 11 commits into
mainfrom
aitools-hint-exempt-commands
Nov 17, 2026
Merged

renaudhartert-db merged 11 commits into
mainfrom
aitools-hint-exempt-commands

Conversation

@renaudhartert-db

@renaudhartert-db renaudhartert-db commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Changes

When a coding agent such as Claude Code or Codex runs the CLI without the Databricks tooling installed, the CLI prints a stderr hint asking the agent to run databricks aitools install. This PR replaces the aitools-only check that skips the hint with isHintExemptCommand, which matches the command's path below the root against one list: aitools, experimental aitools, auth, configure, current-user me, version, completion, help, and cobra's hidden shell-completion command.

MaybeHint keeps its separate check for the auth token and auth docker token credential helpers, although auth covers them. That check protects output that other tools embed mid-line, so it must hold even if auth leaves this list.

On databricks version --check, hinted agents (Claude Code and the registry agents, such as Codex) now get no install nudge: the root hint skips version, and the version-check tip already skips agents that the root hint covers. Other detected agents still get the tip.

Out of scope: the update hint for outdated installs (follow-up PR). That PR exports the predicate and calls it from libs/aitools/installer.

Why

The hint fires on every command outside the aitools tree, including one-shot lookups such as databricks current-user me and databricks version, auth checks, help, and shell completion. The nudge eval measured "who am I" at 0 of 20 conversions: the agent has no task to apply the skills to, so the line is noise. The other entries are the same kind of call; the eval did not measure them separately. Exempt commands do not use up the per-session hint, so the hint still prints on the next non-exempt command.

Tests

  • New TestIsHintExemptCommand table covering exempt and non-exempt paths, including a prefix negative (authz) and an exempt name under a non-exempt parent (bundle help), built with a small local commandAt helper.
  • acceptance/cmd/aitools/claude-config-dir triggers the hint with clusters list instead of version, and gains a step showing current-user me prints with no hint.
  • acceptance/cmd/aitools/agent-hints triggers the hint with jobs list, and acceptance/cmd/aitools/telemetry/hint uses bundle schema as its command without auth. acceptance/cmd/version shows no hint for Claude Code and Codex.
  • go test ./libs/aitools/... ./cmd/root/..., the acceptance suite outside bundle/, and golangci-lint pass.

This pull request and its description were written by Isaac.

The install hint fires on every command Claude Code runs without the
Databricks tooling, including one-shot lookups such as `current-user me`,
auth checks, help, and shell completion, where it never converts. Widen the
aitools-only exemption into a shared list behind IsHintExemptCommand.

Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
@github-actions

github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Commit: 6d9ae4783 | Workflow run

Regression test report

Selected 4 changed tests (limit=20, 0 not selected)

4 tests: regression=2 unreleased=2 coverage=0 failing=0
test branch main (479098f) latest (v1.26.0)
TestAccept/cmd/aitools/agent-hints ✅ ✅ ❌
TestAccept/cmd/aitools/claude-config-dir ✅ ❌ ❌
TestAccept/cmd/aitools/telemetry/hint ✅ ✅ ❌
TestAccept/cmd/version ✅ ❌ ❌
TestAccept/cmd/aitools/agent-hints: branch ✅ | main (479098f) ✅ | latest (v1.26.0) ❌

latest (v1.26.0):

acceptance_test.go:1380: Diff:
        --- cmd/aitools/agent-hints/output.txt
        +++ /tmp/TestAcceptcmdaitoolsagent-hints3059272519/002/output.txt
        @@ -2,24 +2,20 @@
         === Codex is hinted once per thread
         
         >>> CODEX_CI=1 CODEX_THREAD_ID=thread-1 [CLI] jobs list
        -Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install --agents codex --scope global
         
         >>> CODEX_CI=1 CODEX_THREAD_ID=thread-1 [CLI] jobs list
         
         >>> CODEX_CI=1 CODEX_THREAD_ID=thread-2 [CLI] jobs list
        -Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install --agents codex --scope global
         
         === Cursor exposes no session id, so it is hinted once per machine
         
         >>> CURSOR_AGENT=1 [CLI] jobs list
        -Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install --agents cursor --scope global
         
         >>> CURSOR_AGENT=1 [CLI] jobs list
         
         === Copilot CLI maps to the copilot registry agent
         
         >>> COPILOT_CLI=1 [CLI] jobs list
        -Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install --agents copilot --scope global
         
         === Gemini CLI with its own Databricks skills is not hinted
TestAccept/cmd/aitools/claude-config-dir: branch ✅ | main (479098f) ❌ | latest (v1.26.0) ❌

main (479098f):

acceptance_test.go:1380: Diff:
        --- cmd/aitools/claude-config-dir/output.txt
        +++ /tmp/TestAcceptcmdaitoolsclaude-config-dir3982267918/002/output.txt
        @@ -18,6 +18,8 @@
         === Exempt commands never hint, even without the tooling
         
         >>> CLAUDE_CONFIG_DIR=missing [CLI] current-user me
        +<claude-code-hint v="1" type="plugin" value="databricks@claude-plugins-official" />
        +Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install
         json.userName = "[USERNAME]";
         
         === Empty override uses the default installation
        
FAIL

latest (v1.26.0):

acceptance_test.go:1380: Diff:
        --- cmd/aitools/claude-config-dir/output.txt
        +++ /tmp/TestAcceptcmdaitoolsclaude-config-dir2387614698/002/output.txt
        @@ -9,7 +9,6 @@
         === Custom directory takes precedence over the default installation
         
         >>> CLAUDE_CONFIG_DIR=missing [CLI] clusters list
        -<claude-code-hint v="1" type="plugin" value="databricks@claude-plugins-official" />
         Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install
         ID    Name                State
         4321  some-test-cluster   
        @@ -18,6 +17,7 @@
         === Exempt commands never hint, even without the tooling
         
         >>> CLAUDE_CONFIG_DIR=missing [CLI] current-user me
        +Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install
         json.userName = "[USERNAME]";
         
         === Empty override uses the default installation
        @@ -45,7 +45,6 @@
         === Within one session both lines print once, so 2>&1 pipelines see them only on the first command
         
         >>> [CLI] clusters list
        -<claude-code-hint v="1" type="plugin" value="databricks@claude-plugins-official" />
         Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install
         ID    Name                State
         4321  some-test-cluster   
        
FAIL
TestAccept/cmd/aitools/telemetry/hint: branch ✅ | main (479098f) ✅ | latest (v1.26.0) ❌

latest (v1.26.0):

acceptance_test.go:1248: Substituted DATABRICKS_CLI_GITHUB_API_URL "$DATABRICKS_HOST" -> "http://127.0.0.1:41719" ("[DATABRICKS_HOST]")
    acceptance_test.go:1248: Substituted DATABRICKS_SKILLS_BASE_URL "$DATABRICKS_HOST" -> "http://127.0.0.1:41719" ("[DATABRICKS_HOST]")
    acceptance_test.go:1380: 
        	Error Trace:	/home/runner/work/cli/cli/libs/testdiff/testdiff.go:22
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:1380
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:1121
        	            				/home/runner/work/cli/cli/acceptance/acceptance_test.go:666
        	Error:      	Not equal: 
        	            	expected: "\n=== hint printed on an authenticated command: one hint-shown event per printed line is uploaded\n\n>>> [CLI] jobs list\n<claude-code-hint v=\"1\" type=\"plugin\" value=\"databricks@claude-plugins-official\" />\nDatabricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install\n\n>>> print_telemetry\n{\"command\":\"jobs_list\",\"exit_code\":0,\"aitools_hint_event\":{\"hint_kind\":\"CLAUDE_CODE_NATIVE\"}}\n{\"command\":\"jobs_list\",\"exit_code\":0,\"aitools_hint_event\":{\"hint_kind\":\"INSTALL_TEXT\"}}\n\n=== hint printed on a command that resolves no auth: nothing is uploaded\n\n>>> [CLI] bundle schema\n<claude-code-hint v=\"1\" type=\"plugin\" value=\"databricks@claude-plugins-official\" />\nDatabricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install\n\n>>> print_telemetry\n\n=== plugin installed: no hint, no event\n\n>>> [CLI] jobs list\n\n>>> print_telemetry\n"
        	            	actual  : "\n=== hint printed on an authenticated command: one hint-shown event per printed line is uploaded\n\n>>> [CLI] jobs list\nDatabricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install\n\n>>> print_telemetry\n\n=== hint printed on a command that resolves no auth: nothing is uploaded\n\n>>> [CLI] bundle schema\nDatabricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install\n\n>>> print_telemetry\n\n=== plugin installed: no hint, no event\n\n>>> [CLI] jobs list\n\n>>> print_telemetry\n"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -4,3 +4,2 @@
        	            	 >>> [CLI] jobs list
        	            	-<claude-code-hint v="1" type="plugin" value="databricks@claude-plugins-official" />
        	            	 Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install
        	            	@@ -8,4 +7,2 @@
        	            	 >>> print_telemetry
        	            	-{"command":"jobs_list","exit_code":0,"aitools_hint_event":{"hint_kind":"CLAUDE_CODE_NATIVE"}}
        	            	-{"command":"jobs_list","exit_code":0,"aitools_hint_event":{"hint_kind":"INSTALL_TEXT"}}
        	            	 
        	            	@@ -14,3 +11,2 @@
        	            	 >>> [CLI] bundle schema
        	            	-<claude-code-hint v="1" type="plugin" value="databricks@claude-plugins-official" />
        	            	 Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install
        	Test:       	TestAccept/cmd/aitools/telemetry/hint
        	Messages:   	cmd/aitools/telemetry/hint/output.txt vs /tmp/TestAcceptcmdaitoolstelemetryhint1212099961/002/output.txt
TestAccept/cmd/version: branch ✅ | main (479098f) ❌ | latest (v1.26.0) ❌

main (479098f):

acceptance_test.go:1380: Diff:
        --- cmd/version/output.txt
        +++ /tmp/TestAcceptcmdversion1780502459/002/output.txt
        @@ -38,11 +38,13 @@
         === version --check from Claude Code prints no hint
         
         >>> [CLI] version --check
        +Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install
         Databricks CLI v[CLI_VERSION]
         This is a development build; skipping the update check.
         
         === version --check from Codex prints no hint
         
         >>> [CLI] version --check
        +Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install --agents codex --scope global
         Databricks CLI v[CLI_VERSION]
         This is a development build; skipping the update check.

latest (v1.26.0):

acceptance_test.go:1380: Diff:
        --- cmd/version/output.txt
        +++ /tmp/TestAcceptcmdversion2229971490/002/output.txt
        @@ -8,7 +8,7 @@
         
         >>> [CLI] version --check
         Databricks CLI v[CLI_VERSION]
        -This is a development build; skipping the update check.
        +Could not reach GitHub to check for a newer version. See https://github.com/databricks/cli/releases for the latest release.
         
         === version --check --output json
         
        @@ -16,15 +16,14 @@
         {
           "current_version": "[CLI_VERSION]",
           "update_available": false,
        -  "development_build": true
        +  "check_failed": true
         }
         
         === version --check with a coding agent and no Databricks tooling
         
         >>> [CLI] version --check
         Databricks CLI v[CLI_VERSION]
        -This is a development build; skipping the update check.
        -Tip: coding agents detected without Databricks skills. Run 'databricks aitools install' to install them.
        +Could not reach GitHub to check for a newer version. See https://github.com/databricks/cli/releases for the latest release.
         
         === version --check --output json with a coding agent prints no tip
         
        @@ -32,17 +25,18 @@
         {
           "current_version": "[CLI_VERSION]",
           "update_available": false,
        -  "development_build": true
        +  "check_failed": true
         }
         
         === version --check from Claude Code prints no hint
         
         >>> [CLI] version --check
        +Databricks skills are not installed. To work with Databricks reliably, first run: databricks aitools install
         Databricks CLI v[CLI_VERSION]
        -This is a development build; skipping the update check.
        +Could not reach GitHub to check for a newer version. See https://github.com/databricks/cli/releases for the latest release.
         
         === version --check from Codex prints no hint
         
         >>> [CLI] version --check
         Databricks CLI v[CLI_VERSION]
        -This is a development build; skipping the update check.
        +Could not reach GitHub to check for a newer version. See https://github.com/databricks/cli/releases for the latest release.

Only the agents tests build command trees, so a shared helper in internal/testutil is not needed.

Co-authored-by: Isaac <no-reply@databricks.com>
@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Integration test report

Commit: 6d9ae47

Run: 43984505912

Env 💚​RECOVERED ✅​pass 🙈​skip Time
💚​ aws linux-2core-8gb 1 270 19 8:18
💚​ aws-windows-latest-4core-16gb 1 272 17 7:29
💚​ azure linux-2core-8gb 1 269 19 10:37
💚​ azure-windows-latest-4core-16gb 1 271 17 6:30
💚​ gcp linux-2core-8gb 1 270 19 8:10
💚​ gcp-windows-latest-4core-16gb 1 272 17 6:15
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb azure linux-2core-8gb azure-windows-latest-4core-16gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
💚​ TestAccept 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
Top 7 slowest tests (at least 2 minutes):
duration env testname
3:37 aws-windows-latest-4core-16gb TestAccept
3:29 gcp-windows-latest-4core-16gb TestAccept
3:10 azure-windows-latest-4core-16gb TestAccept
2:27 azure-windows-latest-4core-16gb TestFilerWorkspaceFilesExtensionsDelete
2:14 azure linux-2core-8gb TestTelemetryEndpoint
2:13 azure linux-2core-8gb TestFilerRecursiveDelete/workspace_files
2:06 aws-windows-latest-4core-16gb TestExportWithFileFlag

renaudhartert-db and others added 2 commits November 10, 2026 23:06
Co-authored-by: Isaac <no-reply@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>

@simonfaltum simonfaltum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review from simonfaltum's review agent (pr-review skill) at 3d91441. Each finding was verified against the code; simonfaltum may follow up.

Not approving yet: 3 open design questions.

This PR replaces the aitools-only hint check with a root-relative exempt list, so Claude Code no longer sees the install hint on auth, configure, current-user me, help, and completion commands. I traced the root pre-run hook and cobra's help and completion handling and found no blocking defects: exempt commands don't use up the per-session hint, both aitools subtrees stay exempt, and CI is green. What remains are three design questions (the speculative export, a second exempt list next to versioncheck, and keeping version hintable), two test-robustness suggestions, and a few small test and comment cleanups.

Questions

  1. IsHintExemptCommand is exported, but nothing outside libs/aitools/agents calls it at this head. The follow-up in libs/aitools/installer could export it when it needs it, since installer already imports agents and no cycle would result. Would you rather keep the export in this PR or move it to the follow-up?
  2. libs/versioncheck/notice.go isExemptCommand already lists completion, help, and __complete, matching on any ancestor name. This PR adds a second list that matches on root-relative paths. Are the two lists meant to stay separate, given that they legitimately differ on version, or should both use one shared predicate for plumbing commands?
  3. version is the same kind of one-shot lookup as current-user me, and versioncheck exempts it. Yet databricks version still hints, while databricks --version never does because cobra returns before the hook. Is keeping version hintable a product decision, or mainly a way to keep the acceptance tests' hint coverage? If the latter, could those tests use another command so that version can be exempt too?

// checks, "who am I", help, shell completion): the agent has no task to apply
// the skills to. Evaluations showed that conversion on these commands is low,
// so a hint on them wastes the prompt.
var hintExemptCommands = []string{

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nice to have] The entries in hintExemptCommands are hard-coded path strings, and TestIsHintExemptCommand builds fake trees with commandAt. Nothing checks that each path exists in the real CLI. If codegen renames current-user/me, or an aitools command moves, the exemption silently stops matching and the unit tests still pass; only the single current-user me acceptance step would catch it. Consider adding a test in an external package (or under cmd/) that builds cmd.New(ctx), resolves each entry with Find(strings.Fields(p)), and asserts an exact match.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather not add this one. current-user me is the only generated entry, and the claude-config-dir step already runs it against the real tree; the rest are hand-written commands or cobra constants. The test would also need special cases for cobra's lazily registered help and __complete, and with the predicate now package-private it would have to live in the agents test binary and pull in cmd. Happy to revisit if you feel strongly.

Comment thread libs/aitools/agents/hint.go Outdated

// commandPath returns cmd's path below the root command, e.g. "current-user me",
// so hintExemptCommands holds whatever the root is named.
func commandPath(cmd *cobra.Command) string {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] commandPath re-implements the parent walk that cobra already provides; the walk also exists as commandString in cmd/root. strings.TrimPrefix(cmd.CommandPath(), cmd.Root().CommandPath()+" ") returns the same root-relative path, and cmd/air/air.go:51-52 already uses this pattern. Using it removes the helper and the slices import.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 3238771. I matched against Root().CommandPath() + " " + exempt rather than TrimPrefix, so the root itself never matches an entry.

Comment thread libs/aitools/agents/hint.go Resolved
return cmd
}

func TestIsHintExemptCommand(t *testing.T) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] If strings.HasPrefix(path, exempt+" ") is changed to strings.HasPrefix(path, exempt), every case in TestIsHintExemptCommand still passes. A future top-level command like authz or helpers would then be exempted by mistake. Add a negative case such as {"authz", false} or {"current-user meh", false}.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added authz in 3238771.

Comment thread libs/aitools/agents/hint_test.go Resolved
Comment thread libs/aitools/agents/hint_test.go Outdated
parent.AddCommand(child)

MaybeHint(ctx, child)
MaybeHint(ctx, commandAt("aitools install"))

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] regularCmd() (line 64) returns a parentless current-user command, so under the new path logic its path is "". The tests that expect a hint pass because the path is empty, not because a real non-exempt command is used. Now that commandAt exists, have regularCmd() return something like commandAt("clusters list") so those tests exercise a realistic non-exempt path.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 3238771, it is commandAt("clusters list") now.

renaudhartert-db and others added 2 commits November 11, 2026 18:07
Build the root-relative path from cobra's CommandPath instead of a hand-rolled parent walk. Drop the __completeNoDesc entry: it is an alias of __complete, so Name() never returns it. Give the hint tests a realistic non-exempt command, replace the fake "help jobs" subtree with the plain help command, and add a prefix negative so "authz" is never exempt. Project the current-user me acceptance output to the one field the step needs.

Co-authored-by: Isaac <no-reply@databricks.com>
The version command is the same kind of one-shot lookup as current-user me, and versioncheck already exempts it. The acceptance test now triggers the hint with clusters list, which runs the pre-run hook against the fake server. Nothing outside the package calls the predicate yet, so it is unexported until the update hint needs it.

Co-authored-by: Isaac <no-reply@databricks.com>
@renaudhartert-db

Copy link
Copy Markdown
Contributor Author

Thanks for the thorough pass. On the three questions:

  1. Export: agreed, nothing calls it here. It is package-private now (b85bd34). The update-hint follow-up exports it with its first external caller.
  2. Two lists: I think they should stay separate. They encode different policies: versioncheck protects machine-readable output, this list is about hint conversion. The overlap is three plumbing names; a shared predicate would couple the two for little gain, and the lists still differ on everything else.
  3. version: fair point, it is the same kind of lookup. It is exempt now (b85bd34). The acceptance tests trigger the hint with clusters list instead.

Co-authored-by: Isaac <no-reply@databricks.com>

@simonfaltum simonfaltum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review from simonfaltum's review agent (pr-review skill) at 83b8607. Each finding was verified against the code; simonfaltum may follow up.

Not approving yet: 1 open design question.

This PR replaces the aitools-only check with a root-relative exempt list, so Claude Code stops seeing the install hint on auth, configure, current-user me, version, help, and shell-completion commands. I traced the matching against cobra (CommandPath, the __completeNoDesc alias, lazy help/complete registration, and --help returning before the pre-run hook) and found no defects. Both aitools mounts stay exempt, exempt commands don't use up the per-session hint, and CI is green. One open question is whether the eval evidence covers auth and configure; beyond that, only small test and description nits remain.

Questions

  1. The comment above hintExemptCommands says evaluations showed low conversion on all of these commands, but the description cites only the "who am I" result (0 of 20). Did the eval also cover auth and configure? Those often run right before real work, and since exempt commands don't record the session marker, the hint still lands on the next non-exempt command. If they weren't measured, would you narrow the comment to what was measured, keep the entries as a judgment call, or drop them until there's data?

Comments outside the changed lines

  • [nit] .github/PULL_REQUEST_TEMPLATE.md: Two description fixes. First, .agents/skills/pr-checklist/SKILL.md asks bodies to keep the template's ## Changes, ## Why, ## Tests headings; this one has no ## Why, and the eval reason sits inside Changes. Second, "the list holds for both the databricks and the pipelines binary" doesn't match this tree: there is a single databricks root (cmd/root/root.go:29), and nothing switches on the executable name. Please move the reason under ## Why and drop or reword the pipelines sentence.

Agreeing with existing threads

  • [nice to have] Exempt list is not checked against the real command tree: #7452 (comment)

Comment thread libs/aitools/agents/hint.go Outdated
// tooling hint prints. Paths are relative to the root command. The aitools
// trees are exempt because telling the agent to run aitools while it already
// runs aitools makes no sense. The rest are plumbing or one-shot lookups (auth
// checks, "who am I", version, help, shell completion): the agent has no task to apply

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] This line of the hintExemptCommands doc comment is 87 characters, while the lines around it wrap near 78, so the paragraph reads raggedly ("...(auth" / "checks, ... to apply" / "the skills to."). It looks like it wasn't reflowed after version was added. Please re-wrap the paragraph to the same width as the rest of the comment.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 34addb8.

return cmd
}

func TestIsHintExemptCommand(t *testing.T) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] No case in the table puts an exempt name under a non-exempt parent. If the matching went back to the old walk that compares Name() at any depth, every current case, including authz and current-user, would still pass. Add a case such as {"bundle help", false} or {"clusters version", false} so that regression fails.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 34addb8.

trace CLAUDE_CONFIG_DIR=missing $CLI clusters list

title "Exempt commands never hint, even without the tooling"
trace CLAUDE_CONFIG_DIR=missing $CLI current-user me | jq .userName

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] This step pulls one field with inline jq .userName, but .agents/rules/testing.md prefers gron.py | grep <field> for single-value lookups, because gron prints the JSON path into the golden output. Consider trace CLAUDE_CONFIG_DIR=missing $CLI current-user me | gron.py | grep userName.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 34addb8.

@pietern pietern added the aitools AI tools (databricks aitools) related changes label Nov 16, 2026
renaudhartert-db and others added 2 commits November 16, 2026 23:30
The exempt-list comment now says the nudge eval measured only "who am I",
and the paragraph is re-wrapped. A "bundle help" case fails if matching
regresses to comparing Name() at any depth. The current-user me step uses
gron.py instead of an inline jq path.

Co-authored-by: Isaac <no-reply@databricks.com>
Main added hints for non-Claude agents, Claude Code's native hint line,
hint telemetry, and a credential-helper check for auth token and auth
docker token. isHintExemptCommand replaces main's isAIToolsCommand; the
credential-helper check stays separate because it guards output other
tools embed, not conversion.

version is exempt, so the acceptance tests that used it to trigger the
hint use jobs list, clusters list, or bundle schema instead. On version
--check, hinted agents now get no nudge: the version-check tip already
skips them. Tests that rooted the tree at aitools use commandAt.

Co-authored-by: Isaac <no-reply@databricks.com>
@renaudhartert-db

Copy link
Copy Markdown
Contributor Author

Thanks. On the second pass:

  1. Eval coverage: only "who am I" was measured. The comment now says so (34addb8). I kept auth and configure as a judgment call: exempt commands don't use up the session hint, so it still prints on the next real command.
  2. Description: done. The reason is under ## Why, and the pipelines sentence is gone.
  3. Real-tree check: same answer as in the thread.

I also merged main and resolved the conflicts with #7585 and #7586; the description lists what changed (the credential-helper check stays, and the tests that used version to trigger the hint use other commands).

@simonfaltum simonfaltum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review from simonfaltum's review agent (pr-review skill) at 6d9ae47. Each finding was verified against the code; simonfaltum may follow up.

No blocking issues found, approving. 5 non-blocking comment(s) below.

This PR replaces the aitools-only check with a root-relative exempt list, so coding agents no longer see the install hint on auth, configure, current-user me, version, help, and shell-completion commands. I traced the matching through cobra: the __completeNoDesc alias resolves to __complete, both aitools mounts stay exempt, and exempt commands don't use up the per-session hint. I found nothing blocking, the earlier questions are all answered, and CI is green. The five nits cover a guard comment on the now-overlapping credential-helper check, two misleading auth test names, a /dev/null redirect that should go to a LOG file, the telemetry README leaving out configure, and an acceptance case that no longer exercises the self-exec guard.

Accepted answers

Comments outside the changed lines

  • [nit] libs/aitools/agents/hint_test.go:417: "other auth command still hints" (and "other auth docker command still hints" at line 433) build trees rooted at auth, so they check only that the credential-helper predicate is narrow. Under the real root, databricks auth profiles and databricks auth docker configure print nothing now. Read on their own, the names suggest the opposite. Rename them to say what they test, e.g. "credential-helper check ignores other auth commands".
  • [nit] acceptance/air/image-push/script:65: This case says the auth docker configure child adds no install hint because of the self-exec guard. That child is now exempt through auth, so the case would pass even if the DATABRICKS_CLI_SELF_EXEC check in MaybeHint broke. Non-exempt self-exec children such as apps deploy from apps init keep only the unit test at hint_test.go:442. Consider updating the comment to say what keeps the child quiet now, or covering the guard with a non-exempt child.

if isHintExemptCommand(cmd) {
return
}
if isCredentialHelperCommand(cmd) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] Under the real databricks root, the auth entry in hintExemptCommands already returns before isCredentialHelperCommand runs, so this branch looks dead. The reason it stays (auth token and auth docker token must stay silent even if auth leaves the list) is only in the PR description and the test comment at hint_test.go:403. A later cleanup could drop the check as redundant; if auth is then removed from the list, the hint ends up inside SDK and Terraform error messages. .agents/rules/comments.md asks for a comment on branches kept as guards. Please add one line here, e.g. "Overlaps the auth exemption on purpose: the credential helpers must stay silent even if auth leaves hintExemptCommands."


title "hint printed on a command that resolves no auth: nothing is uploaded"
trace $CLI version
trace $CLI bundle schema > /dev/null

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] .agents/rules/testing.md asks for noisy output to go to LOG.<name>, not /dev/null, so it stays visible under go test -v. Use trace $CLI bundle schema > LOG.schema; the golden still shows only the hint on stderr.

`databricks version`), no install hint event is logged for that hour even though the agent saw the
hint.
hint is never printed on hint-exempt commands (`hintExemptCommands` in
`libs/aitools/agents/hint.go`: aitools, `auth`, one-shot lookups, help, completion) or in CLI

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] The parenthetical lists "aitools, auth, one-shot lookups, help, completion". configure is exempt but is not a lookup, so someone checking why databricks configure logs no hint event won't find it here. Add configure to the list.

@renaudhartert-db
renaudhartert-db added this pull request to the merge queue Nov 17, 2026
Merged via the queue into main with commit 4c8b7a1 Nov 17, 2026
29 checks passed
@renaudhartert-db
renaudhartert-db deleted the aitools-hint-exempt-commands branch November 17, 2026 09:59
@eng-dev-ecosystem-bot

Copy link
Copy Markdown
Collaborator

❌ Integration test report

Commit: 4c8b7a1

Run: 44060699846

Env ❌​FAIL 🟨​KNOWN 🤯​MISS 💚​RECOVERED ✅​pass 🙈​skip Time
❌​ aws linux-2core-8gb 100 3 10 1522 1344 309:50
🤯​ aws-windows-latest-4core-16gb 167 12 1377 1369 347:12
❌​ azure linux-2core-8gb 100 1 12 1502 1352 306:01
❌​ azure-windows-latest-4core-16gb 93 1 12 1428 1379 317:13
❌​ gcp linux-2core-8gb 110 53 12 1449 1348 354:58
🤯​ gcp-windows-latest-4core-16gb 343 9 1191 1375 347:41
526 interesting tests: 392 MISS, 122 FAIL, 9 RECOVERED, 3 KNOWN
Test Name aws linux-2core-8gb aws-windows-latest-4core-16gb azure linux-2core-8gb azure-windows-latest-4core-16gb gcp linux-2core-8gb gcp-windows-latest-4core-16gb
🟨​ TestAccept 🟨​K 🤯​M 🟨​K 🟨​K 🤯​M 🤯​M
🤯​ TestAccept/bundle/apps/job_permissions ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/apps/job_permissions/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/apps/job_permissions/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/artifacts/artifact_path_with_volume/volume_doesnot_exist ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/artifacts/artifact_path_with_volume/volume_doesnot_exist/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/artifacts/artifact_path_with_volume/volume_doesnot_exist/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/artifacts/artifact_path_with_volume/volume_not_deployed ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/artifacts/artifact_path_with_volume/volume_not_deployed/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/artifacts/artifact_path_with_volume/volume_not_deployed/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/config-remote-sync/cluster_policy_cross_target ❌​F 🙈​s ❌​F 🙈​s ❌​F 🙈​s
❌​ TestAccept/bundle/config-remote-sync/cluster_policy_cross_target/DMS= ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/config-remote-sync/cluster_policy_cross_target/DMS=true ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/config-remote-sync/cluster_policy_remote_addition ❌​F 🙈​s ❌​F 🙈​s ❌​F 🙈​s
❌​ TestAccept/bundle/config-remote-sync/cluster_policy_remote_addition/DMS= ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/config-remote-sync/cluster_policy_remote_addition/DMS=true ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/config-remote-sync/policy_injected_cluster_fields ❌​F 🙈​s ❌​F 🙈​s ❌​F 🙈​s
❌​ TestAccept/bundle/config-remote-sync/policy_injected_cluster_fields/DMS= ❌​F ❌​F ❌​F
❌​ TestAccept/bundle/config-remote-sync/policy_injected_cluster_fields/DMS=true ❌​F ❌​F ❌​F
🤯​ TestAccept/bundle/debug/fetch-repository-info ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/debug/fetch-repository-info/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/debug/fetch-repository-info/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/empty-bundle ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/empty-bundle/DATABRICKS_BUNDLE_ENABLE_EXPERIMENTAL_YAML_SYNC=/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/empty-bundle/DATABRICKS_BUNDLE_ENABLE_EXPERIMENTAL_YAML_SYNC=/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/empty-bundle/DATABRICKS_BUNDLE_ENABLE_EXPERIMENTAL_YAML_SYNC=true/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/empty-bundle/DATABRICKS_BUNDLE_ENABLE_EXPERIMENTAL_YAML_SYNC=true/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/files/no-snapshot-sync ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/files/no-snapshot-sync/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/files/no-snapshot-sync/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/basic ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/basic/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/breakglass ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/breakglass/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/can-manage ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/can-manage/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/destroy-redeploy ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/destroy-redeploy/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/dev-mode ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/dev-mode/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/legacy-state ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/legacy-state/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/missing-snapshot ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/missing-snapshot/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/no-artifacts ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/no-artifacts/DMS=/READPLAN= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/no-artifacts/DMS=/READPLAN=1 ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/permissions-change ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/permissions-change/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/select ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/immutable/select/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/mlops-stacks ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/mlops-stacks/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deploy/mlops-stacks/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/deploy/spark-jar-task ❌​F 🤯​M ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/deploy/spark-jar-task/DMS= ❌​F 🤯​M ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/deploy/spark-jar-task/DMS=true ❌​F 🤯​M ❌​F ❌​F ❌​F ✅​p
🤯​ TestAccept/bundle/deployment/bind/alert ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deployment/bind/alert/DMS= ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deployment/bind/alert/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deployment/bind/catalog ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
🤯​ TestAccept/bundle/deployment/bind/catalog/DMS=true ✅​p 🤯​M ✅​p ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/deployment/bind/pipelines/recreate ✅​p ✅​p ✅​p ✅​p ❌​F ✅​p
❌​ TestAccept/bundle/deployment/bind/pipelines/recreate/DMS=true ✅​p ✅​p ✅​p ✅​p ❌​F ✅​p
❌​ TestAccept/bundle/dms/deployment-metadata-change ❌​F ✅​p ✅​p ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/dms/deployment-metadata-change/DMS=true ❌​F ✅​p ✅​p ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/dms/stale-plan ✅​p ✅​p ✅​p ✅​p ❌​F ✅​p
❌​ TestAccept/bundle/dms/stale-plan/DMS=true/READPLAN=1 ✅​p ✅​p ✅​p ✅​p ❌​F ✅​p
❌​ TestAccept/bundle/dms/successful-recreate ❌​F ✅​p ✅​p ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/dms/successful-recreate/DMS=true ❌​F ✅​p ✅​p ✅​p ✅​p ✅​p
❌​ TestAccept/bundle/invariant/continue_293 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/continue_293/DMS=/INPUT_CONFIG=cluster.yml.tmpl ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/continue_293/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/continue_293/DMS=/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/continue_293/DMS=/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/continue_293/DMS=/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/continue_293/DMS=/INPUT_CONFIG=job_with_task.yml.tmpl ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=job_apply_policy_default_values_for_each_task.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=job_apply_policy_default_values_task_cluster.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN= ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
❌​ TestAccept/bundle/invariant/no_drift/DMS=true/INPUT_CONFIG=job_with_task.yml.tmpl/READPLAN=1 ❌​F ✅​p ❌​F ❌​F ❌​F ✅​p
💚​ TestAccept/bundle/resources/apps/lifecycle-started 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started/DMS= 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
💚​ TestAccept/bundle/resources/apps/lifecycle-started/DMS=true 💚​R 💚​R 💚​R 💚​R 💚​R 💚​R
❌​ TestAccept/bundle/resources/cluster_policies/definition_multiline ✅​p ✅​p ✅​p ✅​p ❌​F ✅​p
Top 50 slowest tests (at least 2 minutes):
duration env testname
15:28 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
13:37 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
13:22 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=true
12:47 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
12:22 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
12:22 gcp linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
11:55 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
11:25 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
11:22 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
10:37 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
10:33 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
10:33 gcp-windows-latest-4core-16gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=1
10:30 aws-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
10:18 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=
10:01 aws linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:57 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:53 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/materialization_sets/immutable/DMS=true
9:51 azure linux-2core-8gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
9:36 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=
9:29 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=true
9:07 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=
8:33 gcp-windows-latest-4core-16gb TestAccept/pipelines/run/refresh-flags
8:29 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/materialization_sets/batch/DMS=true
8:24 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started/DMS=true
8:24 azure-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started/DMS=
7:43 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/local_ssd_count/DMS=
7:08 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=true
7:04 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/materialization_sets/immutable/DMS=
7:02 gcp-windows-latest-4core-16gb TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=
7:00 aws-windows-latest-4core-16gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_libraries.yml.tmpl/READPLAN=
6:53 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/data_security_mode/DMS=true
6:49 aws linux-2core-8gb TestAccept/bundle/apps/job_permissions/DMS=
6:46 aws-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/deploy/simple/DMS=true
6:44 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/materialization_sets/batch/DMS=
6:44 gcp-windows-latest-4core-16gb TestAccept/bundle/invariant/no_drift/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=
6:31 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/lifecycle-started-toggle/DMS=true
6:27 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/clusters/resize-terminated-fallback/DMS=true
6:24 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=true
6:17 gcp linux-2core-8gb TestAccept/bundle/config-remote-sync/multiple_resources/DMS=
6:13 gcp linux-2core-8gb TestAccept/bundle/templates/default-python/combinations/classic/DLT=no/DMS=/NBOOK=yes/PY=yes/READPLAN=1
6:12 gcp-windows-latest-4core-16gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=registered_model.yml.tmpl/READPLAN=
6:02 gcp-windows-latest-4core-16gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_apply_policy_default_values_job_cluster.yml.tmpl/READPLAN=1
6:00 aws-windows-latest-4core-16gb TestAccept/bundle/invariant/destroy_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=1
5:58 gcp linux-2core-8gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_with_depends_on.yml.tmpl/READPLAN=1
5:56 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started-omitted/DMS=true
5:56 gcp linux-2core-8gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=job_table_update_trigger.yml.tmpl/READPLAN=
5:54 aws-windows-latest-4core-16gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster.yml.tmpl/READPLAN=
5:51 aws linux-2core-8gb TestAccept/bundle/config-remote-sync/external_cluster_policy_cross_target/DMS=true
5:50 gcp-windows-latest-4core-16gb TestAccept/bundle/resources/apps/lifecycle-started-toggle/DMS=true
5:48 aws-windows-latest-4core-16gb TestAccept/bundle/invariant/delete_idempotent/DMS=/INPUT_CONFIG=cluster_apply_policy_default_values.yml.tmpl/READPLAN=
(380 table rows omitted to keep the report under 60000 bytes)

deco-sdk-tagging Bot added a commit that referenced this pull request Nov 19, 2026
## Release v1.27.0

### Notable Changes

 * `databricks aitools install`, `update` and `uninstall` now exit with code 1 when they do nothing they were asked to. `install` fails when it sets up nothing: no coding agent is detected, every agent is skipped or fails to install, or no skill in the release can be installed (also with `--path`). `update` fails when every update or check it attempts fails, and `uninstall` when every removal it attempts fails. Scripts that ran these commands as a best-effort step and relied on exit code 0 should handle the new exit code. ([#7481](#7481))
 * Add `file:<path>` selectors to `pipelines run` and pipeline `bundle run`. `--refresh` and `--full-refresh` now use space-separated lists, such as `--refresh "orders payments"`, instead of comma-separated lists. Single names containing spaces now require backticks, e.g. ``--refresh 'table:`order details`'``. ([#7184](#7184))
 * The Databricks CLI is now available on PyPI as `databricks`: run it with `uvx databricks`, or install it with `uv tool install databricks`, `pipx install databricks` or `pip install databricks`. The package contains only the prebuilt CLI binary. Uninstall the legacy `databricks-cli` package first, since both install a `databricks` command. ([#7704](#7704), [#7777](#7777))

### CLI

 * Add `databricks sandbox fs` commands (`cp`, `ls`, `cat`, `mkdir`, `rm`) to transfer files between your local filesystem and sandboxes using `<sandbox-id>:/path`. ([#7372](#7372))
 * `databricks fs` commands retry reads (stat, list, open) and deletes on DBFS and Volumes when the server returns a transient error or does not respond within the HTTP timeout. ([#7556](#7556))
 * Retry UC Volumes file operations (`fs cp`, `fs ls`, `fs rm`, bundle uploads to Volumes) when the Files API returns HTTP 408, 429, 502, 503 or 504 (for example "AWS S3 is throttling requests"), or on a transient network error; this regressed in v1.10.0. ([#7559](#7559))
 * Stop warning when the host metadata request (`/.well-known/databricks-config`) times out; the CLI already falls back to your config, and the message is still shown with `--debug`. ([#7752](#7752))
 * Add `databricks aitools auto-install disable` and `enable` to turn off (or back on) the automatic installation of Databricks AI tools on CLI upgrades. A global-scope `databricks aitools uninstall` also turns it off. ([#7701](#7701))
 * Stop printing the Databricks AI tooling install hint on `auth`, `configure`, `current-user me`, `version`, `help`, and shell-completion commands. ([#7452](#7452))
 * When Codex, Cursor, GitHub Copilot CLI, OpenCode, Gemini CLI, Antigravity, Pi, Goose or Kiro run the CLI without Databricks skills installed for that agent, the CLI now prints a one-line hint to install them with `databricks aitools install --agents <agent> --scope global`, previously shown only to Claude Code. ([#7586](#7586))
 * `databricks aitools install` now rejects an unknown `--agents` name before it shows the scope prompt, instead of after. ([#7469](#7469))
 * `databricks aitools install` no longer asks "Proceed?" after the agent picker; the picker selection confirms the plan. The picker title now shows the install scope, its hint says Enter installs, `--skills-only` runs label plugin agents "skills" and pre-check every agent whose config dir exists, and the plan summary after it is reduced to the scope line. ([#7478](#7478))
 * `databricks aitools install --output json` reports more specific `error_category` values: `SKILLS_FETCH_FAILED`, `RELEASE_LOOKUP_FAILED`, `RATE_LIMITED`, `MANIFEST_INVALID`, `STATE_INVALID` and `PLUGIN_CLI_TIMEOUT`. A coding agent CLI that does not answer in time is now reported as `timed out after <duration>`, followed by any stderr it wrote before it was stopped. ([#7475](#7475))
 * `databricks aitools install` no longer prompts when a coding agent runs it, even in a pseudo-terminal; it uses the non-interactive defaults instead and prints a note saying so. ([#7477](#7477))
 * `databricks aitools install` now prints the directory it installed skills into (for example `Installed 1 skill in ~/.databricks/aitools/skills.`), so agents can open the installed `SKILL.md` files without searching for them. ([#7668](#7668))
 * `databricks aitools install` now ends a failed install with a step to recover, in the text output and in a new `recovery` field of `--output json`. ([#7480](#7480))
 * `databricks aitools install` now installs plugins for the other coding agents even when installing skill files fails. ([#7479](#7479))
 * `databricks aitools install` now installs skill files for a detected coding agent whose CLI is not on PATH (for example a Claude Code desktop or IDE install), unless it already has the plugin, says how to switch to the plugin later, and warns when the current project also has the plugin. `databricks aitools update` no longer tries to install the plugin for such an agent, and no longer writes skill files next to a plugin that such an agent already has. ([#7482](#7482))
 * Fix `databricks aitools install` waiting a long time on an unreachable or slow workspace while it resolves authentication for telemetry; that wait is now limited to a few seconds. ([#7468](#7468))
 * `databricks aitools install`, `update` and `list` now refuse a skills manifest that names a skill or file outside the skills directory, before writing any skill files. A skill whose name or file paths are not portable is skipped with a warning, and `update` keeps its installed copy. ([#7722](#7722))
 * `databricks aitools install` and `databricks aitools update` refresh only the marketplace the Databricks plugin is listed in, so another unreachable marketplace no longer blocks them. When that refresh fails, both commands warn, install or update the plugin from the local copy of the marketplace, and record the plugin version as unknown. ([#7473](#7473))
 * `databricks aitools install` and `databricks aitools update` now wait up to 20 seconds instead of 5 for a coding agent's CLI to answer the plugin capability check, so a slow first start is less likely to report the agent as unavailable. ([#7472](#7472))
 * `databricks aitools install` no longer fails a plugin-only install when the lookup of the latest skills release on GitHub fails or is rate-limited. The plugin is installed and its version is recorded as unknown. ([#7474](#7474))
 * `databricks aitools` commands now send usage telemetry, and the CLI records when it recommends installing Databricks AI tools. When the configured workspace is slow or unreachable, `aitools install`, `update` and `uninstall` can take up to about 6 seconds longer, and `list`, `version` and runs that stop early up to about 3 seconds. Set `DATABRICKS_CLI_DISABLE_TELEMETRY=1` to opt out. ([#7467](#7467), [#7469](#7469), [#7470](#7470))
 * `databricks aitools install` and `databricks aitools update` now report a coding agent CLI shim (`.cmd` or `.bat`) on Windows that prints its plugin help and then exits with an error as `shim-exited-with-error`, with the command to run to see the error, instead of reporting the CLI as not on PATH. ([#7476](#7476))
 * `apps init` no longer suggests installing skills when every detected coding agent already has the Databricks plugin. ([#7467](#7467))
 * `databricks auth login` now gives up on the optional workspace lookup after about 5 seconds instead of retrying for about 5 minutes, and explains the fallback to the manual workspace ID prompt. ([#7522](#7522))
 * Throttle Claude Code's native plugin install hint separately from the text hint: it prints at most once per 10 minutes per session, so the install dialog still comes up when a subagent, a hook, or a command outside a Claude Code subprocess runs the session's first `databricks` command. ([#7692](#7692))
 * Print Claude Code's native plugin install hint alongside the text hint, so Claude Code offers a one-click install of the Databricks plugin. Claude Code now counts as having the tooling only when it loads it: skills only in `~/.databricks/aitools/skills` don't count, and a project- or local-scope plugin counts only when the CLI runs inside that project. `auth token`, `auth docker token` and CLI subprocesses no longer print install hints. ([#7585](#7585))
 * Interactive prompts and pagers now work in Git for Windows' bash and other MSYS2 shells when they run under ConPTY (the default since Git for Windows 2.47) or directly in a Windows console. ([#7699](#7699))
 * Add the `databricks feedback` command to send feedback about the CLI to Databricks. ([#7724](#7724))
 * Fix shell completion in `databricks fs` commands for local paths typed with a leading `./` or repeated separators, which previously offered no suggestions. ([#7679](#7679))
 * Fix a panic in `databricks labs` commands when a non-string SDK setting such as `DATABRICKS_DEBUG_HEADERS` or `DATABRICKS_RATE_LIMIT` is set in the environment. ([#7673](#7673))
 * Fix a panic in `databricks labs install` for projects whose `labs.yml` has no `install` section. ([#7673](#7673))
 * `NO_COLOR` no longer disables prompts, spinners or the list pager; they run without color. ([#7700](#7700))
 * Add the Beta `databricks pipelines test` command, which runs the tests of a pipeline, and the `testing` property of pipelines in bundles. ([#7429](#7429))
 * Add `databricks sandbox forward`, which serves an app running in a sandbox at a local URL. ([#7395](#7395))
 * Bound the whole telemetry upload at exit, including config resolution and authentication, by its timeout, so a stalled auth or telemetry endpoint no longer keeps a command from exiting. ([#7467](#7467))
 * `databricks version --check` now suggests `databricks aitools install` on stderr when a coding agent is detected without the Databricks plugin or skills. ([#7471](#7471))

### AI Runtime

 * `air get -o json` now reports `PENDING` while the run waits for compute, matching `air list`, and includes the run's `status_message`. ([#7455](#7455))
 * Wrap long failure reasons and log lines in the `air list` info and logs panes, keep the MLflow link (labeled with its retry) when a run's last retry failed before starting, and point `air logs` at earlier retries when the last one has no logs. ([#7456](#7456))
 * `databricks air logs --node` now reports an out-of-range node index when it can determine the run's node count, instead of looking like a successful run with no logs. ([#7516](#7516))
 * Add experiment, duration, accelerator, and dashboard metadata to `air list --output json`. For retried runs, `started_at` now reports the latest attempt, matching `air get`. ([#7568](#7568))
 * `air list` shortens MLflow run names and unnamed-run IDs by keeping their end behind a leading `…`, and its columns no longer overflow on wide (for example CJK) text; `air get` shows an unnamed run's full MLflow run ID. ([#7582](#7582))
 * Shrink the Experiment and User columns of the interactive `air list` table to fit the terminal width, keeping the end of a shortened experiment name. ([#7583](#7583))
 * Show the experiment, accelerators and configuration in the `air list` info pane for runs where it showed `N/A`. ([#7587](#7587))
 * Strip terminal control characters from the MLflow run, experiment and user names shown by `air list` and `air get`, so a run name cannot clear or retitle the terminal of whoever lists it. ([#7601](#7601))
 * `air logs`, `air get`, and `air run --watch` no longer make an extra credential-check request before fetching the run, and `air get` reuses the configured workspace ID instead of looking it up. ([#7613](#7613))
 * `air list` no longer waits on extra current-user requests before listing runs, which makes the default list about 150ms faster. ([#7615](#7615))
 * `air list --all-status` requests larger index pages, so it makes far fewer round trips once the server supports `page_size`. ([#7616](#7616))
 * Fit the interactive `air list` table to narrow terminals: when the Experiment and User columns are at their floors, shorten Started to `MM-DD HH:MM` and size the MLflow column to its labels, then hide Accelerators, User, MLflow and Progress in that order, naming the hidden columns in the hint line. ([#7629](#7629))
 * `air get -o json` now includes `mlflow_run_id` and `mlflow_experiment_id`, so a run can be handed to MLflow-based steps without parsing `mlflow_url`. They identify the MLflow run `mlflow_url` links to, including one from an earlier retry that `mlflow_retry` names. ([#7636](#7636))
 * `air get` and the `air list` info pane now show the environment of runs on the Databricks AI environment (`databricks_ai_v*`) instead of `N/A`. ([#7637](#7637))
 * `air run` now rejects a `code_source.include_paths` path that selects no files instead of uploading a snapshot without it; glob patterns and pathspec magic are left to git. ([#7643](#7643))
 * `air convert-to-dabs` now suggests the `--output-dir` that converts a working-tree workload whose `code_source.root_path` is outside the bundle directory, instead of suggesting `sync.paths`. ([#7644](#7644))
 * `air run` now lists a `code_source.root_path` outside a git repository relative to `root_path`, so running from a subdirectory of `root_path` no longer uploads an empty or partial snapshot. ([#7646](#7646))
 * `air list --all-status` now fills `--limit` past purged or inaccessible indexed runs. ([#7743](#7743))
 * `air run` now warns about missing PyTorch when a pinned snapshot's `include_paths` selects a Python file. ([#7744](#7744))
 * `air cancel JOB_RUN_ID` now rejects run IDs that are not AI Runtime runs instead of cancelling unrelated Jobs runs. In `-o json` output, the `failed[].error` text for a run that does not exist or that you cannot view now starts with `failed to get run <id>:` instead of the cancel API error. ([#7569](#7569))
 * `air get -o json` now reports `mlflow_retry` when the MLflow link comes from an earlier retry because the run's last retry never reached MLflow. ([#7620](#7620))
 * `databricks air run --help` now shows how to install the databricks-ai-runtime coding agent skill. ([#7652](#7652))
 * `air run --watch -o json` now reports each lifecycle `STATUS` transition once and never reports a non-terminal state after the run has ended, including when logs are served from MLflow artifacts. ([#7621](#7621))
 * `air convert-to-dabs` now explains the `--output-dir` workaround when `code_source.root_path` resolves to the bundle root, and notes when the generated job carries the default `max_retries`. ([#7579](#7579))
 * `air run` now refuses to upload a `code_source` snapshot that selects no files (for example when `root_path` is git-ignored) and explains the cause, and `--dry-run` runs the snapshot file selection and reports the file count. ([#7570](#7570))
 * Repeat the Jobs run link after live log streaming ends. ([#7571](#7571))
 * `air get -o json` includes run details including flat `accelerator_type` and `num_accelerators`. Use `--include-config` to include stored config, which may contain plaintext `env_variables` and parameters; downloads over 1 MiB are omitted, and config-dependent `max_retries` is otherwise null. ([#7624](#7624))
 * `air get` and the `air list` info pane no longer show `Max Retries 0` when the Jobs API leaves the task's retry limit out. For a run submitted with `air run`, the limit now comes from the run's uploaded config, shown as `3 (CLI default)` when the config doesn't set `max_retries`; it shows `N/A` when the limit can't be known (job runs, multi-container runs, legacy runs with no explicit value, or an unreadable config). ([#7623](#7623))
 * Reorganize `databricks air` help: subcommands are grouped by task, `air run` has examples, and YAML fields are listed under headings, with pool fields marked optional and `command`, `compute.num_accelerators`, and `compute.accelerator_type` correctly marked required. ([#7512](#7512))
 * `air run -h config` now lists the environment variables AI Runtime sets on every node (such as `MLFLOW_RUN_ID` and `CODE_SOURCE_PATH`), and `air logs --help` notes that `--download-to` cannot be combined with `--tail` or `--minutes`. ([#7655](#7655))
 * Support full workspace accelerator types in `air list` filters while preserving family matching, and reject invalid filter values. ([#7515](#7515))
 * `databricks air list --all-status` now warns when the AI Runtime run index is unavailable and it falls back to scanning Jobs runs. That fallback scan is capped at 250 runs, and a stuck index request fails after 15 seconds instead of retrying for minutes. `--all-status --filter user=<your email>` now uses the run index instead of scanning the workspace's full run history. ([#7619](#7619))
 * Return structured JSON errors for invalid `air list --filter` values when `-o json` is used. ([#7612](#7612))
 * `air list --all-status` no longer fails when a listed run has been purged. ([#7523](#7523))
 * **Behavior change:** `databricks air logs` now prints the logs available now and exits, also for an active run, matching `kubectl logs`, `docker logs` and `databricks apps logs`. Pass `--follow` (`-f`) to stream new lines until the run completes; `--tail N --follow` prints the last N lines first. `databricks air run --watch` still submits and streams. ([#7658](#7658))
 * `databricks air logs -o json` and `databricks air run --watch -o json` now emit a `WAITING` event, for example `{"type":"WAITING","message":"Waiting for accelerator compute capacity..."}`, when the reported waiting status changes. ([#7695](#7695))
 * `databricks air logs` on a run that ended in the last two minutes now waits for the log index to settle before printing, instead of sometimes dropping lines that were indexed late. ([#7663](#7663))
 * `air logs` and `air run --watch` now print the waiting status (for example `Waiting for accelerator compute capacity...`) as a line on stderr when stderr is not a terminal, instead of printing nothing until the run produces logs. ([#7657](#7657))
 * Route AIR log links to the MLflow Logs page instead of the hidden artifact path. ([#7491](#7491))
 * Invalid `compute.accelerator_type` errors and `air run -h config.compute` no longer list the CLI's built-in accelerator types, which could differ from the workspace's. ([#7520](#7520))
 * `databricks air --help` now notes that GPU pools are not required to run workloads. ([#7581](#7581))
 * `air run` now prints the job run URL with the `?o=<workspace-id>` suffix, matching `air get` and `air list`; `dashboard_url` in `air run -o json` and the `--watch` events gains it too. When `air list` cannot resolve the workspace ID, its links now omit `?o=` instead of ending in `?o=0`. ([#7573](#7573))
 * `databricks air run` now reports an unknown workload YAML key by its field path, suggests the closest valid field, and points to `-h config` instead of naming an internal Go type. ([#7574](#7574))
 * `air run` (including `--dry-run`) now warns before submitting when the `code_source` imports `torch` but PyTorch is not declared: the environment is the Standard environment (version 5 or later) with no `torch` dependency, so the run may fail after it waits for a GPU. ([#7656](#7656))

### Bundles

 * Add `isolation_mode` to the `catalogs` resource, so a catalog can be deployed as `OPEN` or `ISOLATED`. ([#7463](#7463))
 * `bundle validate` no longer warns when resource permissions and top-level or target permissions name the same principal. ([#7291](#7291))
 * Retry bundle file uploads, reads and deletes when the server does not respond within the HTTP timeout ("request timed out after ... of inactivity"). ([#7521](#7521))
 * Show how to recover when `bundle deploy` fails because an app's service principal does not exist or was deleted. ([#7533](#7533))
 * Retry transient server errors when creating Lakebase (`postgres_*`) resources in the direct deployment engine. ([#7557](#7557))
 * Fix `bundle plan` reporting the `spark_conf` and `custom_tags` the backend derives from `is_single_node: true` as drift on clusters. ([#7577](#7577))
 * Stop planning a spurious update for Lakeflow Connect pipelines whose `ingestion_definition.data_staging_options` is filled in by the backend. ([#7603](#7603))
 * Retry the root path check in `bundle destroy` on transient errors, so a dropped connection no longer fails the destroy. ([#7597](#7597))
 * Use the Lakebase branch when its create request times out but the branch was created, instead of failing the deploy, in the direct deployment engine. ([#7602](#7602))
 * Retry transient server errors when deleting resources in the direct deployment engine. ([#7708](#7708))
 * Use the Lakebase project when its create request times out but the project was created, instead of failing the deploy with "already exists", in the direct deployment engine. ([#7747](#7747))
 * Use the feature, model serving endpoint or dashboard that a create request created despite timing out, instead of failing the deploy, in the direct deployment engine. ([#7757](#7757))
 * Use the Lakebase role when its create request fails with a transient error but the role was created, instead of failing the deploy, in the direct deployment engine. ([#7767](#7767))
 * Use the MCP service, model service or model provider service that a create request created despite failing with a timeout, a 499 or a reset stream, instead of failing the deploy, in the direct deployment engine. Create recovery for features, serving endpoints and dashboards now also covers 499 and reset streams. ([#7782](#7782))
 * Retry app updates and deletes in the direct deployment engine when they fail with 400 BAD_REQUEST because the app compute is `UPDATING`, after waiting for the compute to settle. ([#7606](#7606))
 * Enable drift detection for `source_code_path` and `git_source` on apps. ([#6399](#6399))
 * `bundle destroy` and `bundle deploy` no longer fail with "internal error, missing in state" when the state holds an empty-ID entry left by an interrupted recreate in an older CLI. ([#7676](#7676))
 * Fix a feature whose `full_name` contains uppercase letters being recreated on every deploy. ([#7398](#7398))
 * Fix `bundle deployment bind` (and `bundle generate --bind`) failing with `no such node "resources.internal_immutable_snapshots.immutable"` when `workspace.sync_mode` is `immutable`, as reported in [#7306](#7306). ([#7329](#7329))
 * Retry creating the deployment lock (without `--force-lock`) when the request fails with a transient server error, times out ("request timed out after ... of inactivity") or loses its connection ("unexpected EOF"). ([#7594](#7594))
 * Fix a materialization set member whose `feature_name` contains uppercase letters failing to deploy, or recreating the set on every deploy. ([#7398](#7398))
 * Delete the old resource when its name follows a renamed schema. ([#7718](#7718))
 * Fix `pipelines dry-run` starting a real run when given a job KEY, and a crash in its shell completion. ([#7672](#7672))
 * Rename schemas in place; schemas and volumes follow a renamed catalog or schema. ([#7343](#7343))
 * Fix a panic when validating or deploying jobs with local libraries and serverless job clusters. ([#7725](#7725))
 * Fix `tgz` artifacts with `git` set producing an empty tarball or failing when the bundle is in a subdirectory of the git repository. ([#7674](#7674))
 * Apply `presets.trigger_pause_status` and the development mode pause default to `triggers[]` entries on jobs. ([#7450](#7450))

### Dependency Updates

 * Bump dependencies with known vulnerabilities. ([#7750](#7750))
 * Update the Go SDK to [v0.198.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.198.0). ([#7530](#7530))
 * Update the Go SDK to [v0.199.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.199.0). ([#7584](#7584))
 * Update the Go SDK to [v0.200.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.200.0). ([#7653](#7653))
 * Update the Go SDK to [v0.201.0](https://github.com/databricks/databricks-sdk-go/releases/tag/v0.201.0). ([#7769](#7769))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aitools AI tools (databricks aitools) related changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants