databricks-agentbricks 0.8.0__tar.gz → 0.10.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/PKG-INFO +130 -29
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/README.md +129 -28
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/pyproject.toml +1 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/app.py +3 -3
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/deploy.py +75 -9
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/dev.py +10 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/doctor.py +2 -3
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/permissions.py +8 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/pipeline.py +16 -3
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/telemetry.py +170 -34
- databricks_agentbricks-0.10.0/src/databricks_agentbricks/clients/agent_details_client.py +86 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/apps_client.py +23 -4
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/apps_user_auth_client.py +13 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/conversation_store_client.py +22 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/databricks_cli.py +81 -15
- databricks_agentbricks-0.10.0/src/databricks_agentbricks/clients/output_tail.py +124 -0
- databricks_agentbricks-0.10.0/src/databricks_agentbricks/clients/terminal_relay.py +207 -0
- databricks_agentbricks-0.10.0/src/databricks_agentbricks/clients/workspace_identity.py +37 -0
- databricks_agentbricks-0.10.0/src/databricks_agentbricks/diagnostics.py +58 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/errors.py +44 -5
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/deploy.py +95 -47
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/dev.py +21 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/group.py +112 -4
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/help.py +2 -2
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/projects/agent_project.py +64 -13
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/projects/app_manifest.py +48 -23
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deploy_service.py +42 -21
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/deploy_state.py +31 -7
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/provisioners.py +35 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/dev_service.py +96 -68
- databricks_agentbricks-0.10.0/src/databricks_agentbricks/telemetry/__init__.py +1 -0
- databricks_agentbricks-0.10.0/src/databricks_agentbricks/telemetry/scrub.py +104 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-bricks-workflow/SKILL.md +3 -2
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-bricks-workflow/references/deployment.md +16 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-bricks-workflow/references/state-and-tools.md +22 -3
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/AGENTKIT_CONTRACT.md +2 -2
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/README.md +20 -4
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/agent/agent.py +6 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/pyproject.toml +1 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/runtime/adapter.py +9 -4
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/AGENTKIT_CONTRACT.md +2 -2
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/README.md +20 -3
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/agent/agent.py +4 -2
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/pyproject.toml +1 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/agent/agent.py +2 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/pyproject.toml +1 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/pyproject.toml +1 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-langgraph/CHAT_APP.md +15 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-langgraph/runtime/ui.py +116 -5
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-langgraph/tests/test_demo_ui.py +73 -16
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-langgraph/ui/app.js +496 -58
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-langgraph/ui/index.html +47 -21
- {databricks_agentbricks-0.8.0/src/databricks_agentbricks/templates/ui/agent-openai → databricks_agentbricks-0.10.0/src/databricks_agentbricks/templates/ui/agent-langgraph}/ui/styles.css +471 -79
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-openai/CHAT_APP.md +15 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-openai/runtime/ui.py +116 -5
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-openai/tests/test_demo_ui.py +70 -15
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-openai/ui/app.js +496 -58
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-openai/ui/index.html +47 -21
- {databricks_agentbricks-0.8.0/src/databricks_agentbricks/templates/ui/agent-langgraph → databricks_agentbricks-0.10.0/src/databricks_agentbricks/templates/ui/agent-openai}/ui/styles.css +471 -79
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/_api_client.py +5 -1
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/langgraph/history.py +6 -2
- databricks_agentbricks-0.10.0/src/databricks_agentkit/langgraph/messages.py +186 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/model_upgrades/optimization.py +7 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/openai/__init__.py +4 -0
- databricks_agentbricks-0.10.0/src/databricks_agentkit/openai/models.py +27 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/tool_manifest.py +3 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/.gitignore +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/NOTICE +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/agent_hint.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/__main__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/auth.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/endpoint.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/experimental.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/init.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/mcp.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/memory.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/models.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/prompts.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/sandbox.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/sessions.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/tools.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/tracing.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/api_client_provider.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/app_probe.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/legacy_runtime_store.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/local_ports.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/local_tracing_client.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/managed_runtime_store.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/mlflow_trace_client.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/clients/tracing_client.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/model_upgrade.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/endpoint.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/loadtest.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/permissions.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/render.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/reporter.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/theme.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/presentation/tracing.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/projects/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/projects/config.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/projects/resolver.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/projects/types.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/py.typed +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/reporting.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/app_provisioner.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/config.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/model_binding_provisioner.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/names.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/tool_access.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/deployment/tool_access_provisioner.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/endpoint_service.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/invoke/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/invoke/auth.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/invoke/request.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/invoke/transport.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/loadtest/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/loadtest/_locustfile.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/loadtest/plan.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/loadtest/request.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/loadtest/runner.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/loadtest/streaming.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/tracing/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/tracing/targets.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/services/tracing_service.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/skills.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-bricks-migrate/SKILL.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/.env.example +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/.gitignore +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/AGENTS.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/CLAUDE.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/agent/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/agent/mcps.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/agent/tools/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/agent/tools/sample_tool.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/agent/tools/send_message.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/app.yaml +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/runtime/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/runtime/main.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/tests/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/tests/test_agent.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/tests/test_runtime.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-langgraph/tests/test_workspace.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/.env.example +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/.gitignore +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/AGENTS.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/CLAUDE.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/agent/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/agent/checkpoints.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/agent/mcps.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/agent/tools/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/agent/tools/sample_tool.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/agent/tools/send_message.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/app.yaml +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/runtime/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/runtime/adapter.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/runtime/main.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/tests/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/tests/test_agent.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/tests/test_checkpoints.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/tests/test_runtime.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/agent-openai/tests/test_workspace.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/.env.example +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/.gitignore +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/README.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/agent/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/app.yaml +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/runtime/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/runtime/main.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-langgraph/tests/test_runtime.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/.env.example +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/.gitignore +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/README.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/agent/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/agent/agent.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/app.yaml +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/runtime/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/runtime/main.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/custom-agent-openai/tests/test_runtime.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/sandbox_mcp.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/sandbox_mcp_langgraph.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-langgraph/runtime/main.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-langgraph/ui/agentbricks-mark.png +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-langgraph/ui/markdown-it-15.0.2.min.js +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-openai/runtime/main.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-openai/ui/agentbricks-mark.png +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/templates/ui/agent-openai/ui/markdown-it-15.0.2.min.js +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/_pagination.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/_permissions.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/client.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/langgraph/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/langgraph/genie.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/langgraph/mcp.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/langgraph/memory.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/langgraph/responses.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/langgraph/session_store.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/memory_store.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/model_upgrades/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/models.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/openai/genie.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/openai/history.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/openai/mcp.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/openai/memory.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/openai/sessions.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/py.typed +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/ARCHITECTURE.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/README.md +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/app.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/auth.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/cors.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/durability/__init__.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/durability/execution.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/durability/heartbeat.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/durability/lakebase_runtime_store.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/durability/recovery.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/durability/store.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/errors.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/execution.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/genie.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/mcp_auth.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/model_services.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/prompt_registry.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/runtime.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/session_store_client.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/store.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/tracing.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/types.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/runtime/workspace.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/session_store.py +0 -0
- {databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentkit/timefmt.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: databricks-agentbricks
|
|
3
|
-
Version: 0.
|
|
3
|
+
Version: 0.10.0
|
|
4
4
|
Summary: Agent Bricks CLI and AgentKit SDK for custom agents on Databricks
|
|
5
5
|
Author-email: Databricks <agent-feedback@databricks.com>
|
|
6
6
|
License-File: NOTICE
|
|
@@ -164,11 +164,32 @@ credentials.
|
|
|
164
164
|
|
|
165
165
|
If Databricks SDK default authentication is already configured, you can skip `agentbricks login`.
|
|
166
166
|
You can also pass the global `--profile/-p` option before an individual command, for example
|
|
167
|
-
`agentbricks --profile <profile> tools list`. Use `--output json` for
|
|
167
|
+
`agentbricks --profile <profile> tools list`. Use `--output json` (before or after the command) for
|
|
168
|
+
scripting.
|
|
168
169
|
|
|
169
170
|
The CLI sends best effort command usage telemetry after leaf commands. Its log records the static
|
|
170
171
|
command path, package version, operating system, duration, and process outcome (exit code and, for
|
|
171
|
-
nonzero exits, a bounded error category).
|
|
172
|
+
nonzero exits, a bounded error category). Failures can also include up to 4096 UTF-8 bytes of
|
|
173
|
+
error text in `failure_message`. Error text includes exception messages and fully captured
|
|
174
|
+
failed subprocess output, with recognized credentials, paths, and email addresses scrubbed.
|
|
175
|
+
Combined failure text over 65,536 characters is also omitted before scrubbing.
|
|
176
|
+
Credential assignments, auth headers, credential options, and encoded text cause the remaining
|
|
177
|
+
captured text to be omitted; preceding diagnostic text is retained. This avoids parsing arbitrary
|
|
178
|
+
JSON, YAML, or Python values. Recognizable standalone tokens and private keys are also masked.
|
|
179
|
+
This follows the Asset Bundles minimization pattern and is best effort; other customer content
|
|
180
|
+
may remain in service responses or application output.
|
|
181
|
+
It is labeled `DATA_LABEL_USER_COMMANDS_RESPONSE`, excluded from centralized logfood, and retained
|
|
182
|
+
regionally only where customer logging and encryption policies permit. Error text is omitted for
|
|
183
|
+
parser errors and interruptions. Collection requires Legal approval and schema deployment.
|
|
184
|
+
For `dev`, failure text can include complete child output up to 3072 bytes per captured stream.
|
|
185
|
+
Once a stream exceeds that limit, all its retained text is permanently discarded and replaced with
|
|
186
|
+
`[REDACTED]`, including later plain error messages, because partial output may have lost credential
|
|
187
|
+
context. Short complete output is scrubbed before upload, including private keys. Displayed child
|
|
188
|
+
output is unchanged. With one output stream redirected, the terminal stream is inherited unchanged
|
|
189
|
+
and only the redirected stream is retained. When both streams point to the same regular file, both
|
|
190
|
+
are inherited without capture to preserve their original offsets and redirection behavior.
|
|
191
|
+
Startup milestones remain internal; a killed process or unavailable upload can still leave no event.
|
|
192
|
+
Parameter entries include explicitly supplied options
|
|
172
193
|
and parsed Click defaults with supported typed values, automatically across all commands and
|
|
173
194
|
parent groups. Declare defaults in Click options so the shared emitter can read the resolved
|
|
174
195
|
values; fallbacks applied only inside command callbacks are not visible to Click. Omitted free-form
|
|
@@ -178,9 +199,8 @@ choices contribute an `AGENTBRICKS_CLI_`-prefixed value. Click boolean and numer
|
|
|
178
199
|
contribute their typed values; explicitly supplied non-finite floats and integers outside the log
|
|
179
200
|
schema's 64-bit range remain presence-only, while unsupported defaults are omitted. Hidden and
|
|
180
201
|
deprecated options follow the same policy, and repeated
|
|
181
|
-
options contribute one parameter entry per supplied value, up to 64 entries.
|
|
182
|
-
raw command arguments, paths, IDs,
|
|
183
|
-
messages are omitted. Set
|
|
202
|
+
options contribute one parameter entry per supplied value, up to 64 entries. Parameter telemetry
|
|
203
|
+
omits positional arguments, raw command arguments, paths, IDs, and arbitrary free-form values. Set
|
|
184
204
|
`AGENTBRICKS_DISABLE_TELEMETRY=1` to disable these uploads.
|
|
185
205
|
|
|
186
206
|
Telemetry runs only when a leaf command is invoked, whether its callback succeeds or fails. Help
|
|
@@ -193,6 +213,25 @@ thread, returning sooner if the worker finishes. This is not a delivery guarante
|
|
|
193
213
|
uploads can be lost when the process exits after the allowance expires. Missing credentials or a
|
|
194
214
|
failed upload never change the command result.
|
|
195
215
|
|
|
216
|
+
Deploy and `deployments wait` telemetry includes a random invocation UUID, whether a gated
|
|
217
|
+
agent-details link was printed, the observed deployment state, and whether the process is an
|
|
218
|
+
internal background child. Details links carry the invocation UUID so browser arrivals can be
|
|
219
|
+
joined to the command that printed them. The UUID contains no agent name or authentication data.
|
|
220
|
+
Rollout outcomes are recorded independently of link availability, including failed rollouts;
|
|
221
|
+
preparation failures leave the deployment outcome unspecified.
|
|
222
|
+
`AGENTBRICKS_DISABLE_TELEMETRY=1` also removes these attribution parameters while keeping the link.
|
|
223
|
+
`deployments get` and `deployments list` also attach a per-command UUID to details links.
|
|
224
|
+
All rows from one list share one UUID and one command event; their deployment outcome stays
|
|
225
|
+
unspecified because these commands only read state. List links count as emitted only when JSON
|
|
226
|
+
output or terminal hyperlink rendering preserves their targets. Plain redirected output and
|
|
227
|
+
terminal modes that strip hyperlink targets keep `details_link_emitted=false`; use `--output json`
|
|
228
|
+
to capture the URLs. Group arrivals by the joined event's
|
|
229
|
+
`command_path` to distinguish deploy, wait, get, and list. Count distinct invocation IDs, rather
|
|
230
|
+
than list rows or repeated page loads, for command conversion percentages.
|
|
231
|
+
A wait command has its own invocation ID; it is not another deploy. Exclude background children
|
|
232
|
+
from user-invoked command counts. Link arrivals measure browser opens, including copied links,
|
|
233
|
+
not terminal mouse clicks or proof that the deployer and viewer are the same person.
|
|
234
|
+
|
|
196
235
|
## Quickstart
|
|
197
236
|
|
|
198
237
|
The shortest path from a blank directory to a running and deployed agent:
|
|
@@ -208,6 +247,12 @@ agentbricks deploy # deploy to Databricks as agent-bricks-my-agent
|
|
|
208
247
|
`agentbricks dev` runs the agent locally on `http://localhost:8000`, wrapping the Databricks Apps
|
|
209
248
|
local runtime so local behavior matches a deployment.
|
|
210
249
|
|
|
250
|
+
Memory and session stores are off by default in `agentbricks dev`, even when a store is bound in
|
|
251
|
+
`agent.toml`: the chat app shows "Not connected" for memory, and conversation state stays in
|
|
252
|
+
process. They connect after `agentbricks deploy`. To use real stores locally, set
|
|
253
|
+
`AGENT_MEMORY_STORE` (the Store ID) and `AGENT_SESSION_STORE` (the store name) in the project's
|
|
254
|
+
`.env`.
|
|
255
|
+
|
|
211
256
|
`agentbricks init` records the deployment name in `agent.toml`, so `agentbricks deploy` from the
|
|
212
257
|
project directory deploys a Databricks App named `agent-bricks-my-agent`, provisions the
|
|
213
258
|
stores declared in `agent.toml`, and grants the app's service principal access to the stores and
|
|
@@ -222,6 +267,18 @@ The app's compute starts first and boots while the other resources are provision
|
|
|
222
267
|
deploy stops partway, the app it created is kept: re-run `agentbricks deploy` to resume, or remove
|
|
223
268
|
it with `agentbricks deployments delete agent-bricks-my-agent`.
|
|
224
269
|
|
|
270
|
+
When the workspace has both the Agent Memory Sessions beta and the new Agents UI enabled,
|
|
271
|
+
deploy output also includes an **Agent details** link to the workspace management page. This
|
|
272
|
+
applies to first deploys, redeploys, `--no-wait`, and `deployments wait`.
|
|
273
|
+
`deployments get` shows the same link alongside the app URL; `deployments list` links agent
|
|
274
|
+
names to their details pages and keeps a separate **Open app** link. JSON output adds
|
|
275
|
+
`details_url` when available and retains `url` for the deployed agent. The optional flag lookup
|
|
276
|
+
waits at most two seconds per command, including lists; unavailable or disabled flags omit the
|
|
277
|
+
link without affecting the command.
|
|
278
|
+
When following a local deploy record, `deployments wait` also requires its recorded workspace
|
|
279
|
+
host and ID to match the selected profile. Older records or records without a workspace ID omit
|
|
280
|
+
the management link; the recorded deployment status and invocation URL are still available.
|
|
281
|
+
|
|
225
282
|
### Deploying from a coding agent
|
|
226
283
|
|
|
227
284
|
A first deploy takes ~3 min (mostly starting app compute); redeploys are faster. Either run
|
|
@@ -670,8 +727,9 @@ it in `recall` and `list_memories`. `memory_tools` resolves the store from the `
|
|
|
670
727
|
binding, carried to the runtime by the `AGENT_MEMORY_STORE` env var that `agentbricks deploy`
|
|
671
728
|
injects, and returns no tools when no store is set, so the agent runs unchanged.
|
|
672
729
|
That "no store set" path is also how it runs under `agentbricks dev`, which runs locally: memory is off
|
|
673
|
-
there (the store is provisioned and used only at deploy)
|
|
674
|
-
|
|
730
|
+
by default there (the store is provisioned and used only at deploy), even when a store is bound in
|
|
731
|
+
`agent.toml`. Setting `AGENT_MEMORY_STORE` in the project's `.env` uses that store locally. The
|
|
732
|
+
OpenAI Agents adapter exposes the same tools as `databricks_agentkit.openai.memory_tools(actor)`:
|
|
675
733
|
|
|
676
734
|
```python
|
|
677
735
|
from databricks_agentkit.langgraph import memory_tools
|
|
@@ -708,8 +766,8 @@ agentbricks memory stores permissions revoke memory-stores/<id> \
|
|
|
708
766
|
|
|
709
767
|
Session stores accept their configured name or `session-stores/<name>`. Memory stores accept an ID
|
|
710
768
|
or `memory-stores/<id>`; permission Get also accepts the display-name lookup supported by store Get
|
|
711
|
-
and rejects ambiguous matches. The global `--profile`
|
|
712
|
-
`
|
|
769
|
+
and rejects ambiguous matches. The global `--profile` option goes before `sessions` or `memory`;
|
|
770
|
+
`--output json` goes before or after the command. List follows the existing CLI pagination convention: one JSON/piped page
|
|
713
771
|
with `next_page_token`, interactive text pages, or every page with `--all`.
|
|
714
772
|
|
|
715
773
|
Get always returns the authenticated caller's effective permission, including
|
|
@@ -754,8 +812,8 @@ trusted application context. The chat app sends the signed-in user; HTTP clients
|
|
|
754
812
|
`agentbricks endpoint invoke`, have to send it themselves. With a request-user (`auth = "user"`) tool
|
|
755
813
|
bound, the runtime also namespaces a supplied `actor` to the signed-in user.
|
|
756
814
|
|
|
757
|
-
Memory is off under `agentbricks dev`, so try this against a deployed agent: two
|
|
758
|
-
actor.
|
|
815
|
+
Memory is off by default under `agentbricks dev`, so try this against a deployed agent: two
|
|
816
|
+
conversations, one actor.
|
|
759
817
|
|
|
760
818
|
```sh
|
|
761
819
|
ask() { agentbricks --profile <profile> endpoint invoke agent-bricks-my-agent --path /api/invocations \
|
|
@@ -764,6 +822,37 @@ ask "Remember that I prefer answers as bullet points." # conversation 1 saves a
|
|
|
764
822
|
ask "How do I like my answers formatted?" # conversation 2 recalls it
|
|
765
823
|
```
|
|
766
824
|
|
|
825
|
+
### Seeding and using memory from the CLI
|
|
826
|
+
|
|
827
|
+
There are two ways to get a memory store behind a deployed agent. Both end with
|
|
828
|
+
`agentbricks deploy`, which creates the store if it doesn't exist and grants the app access to it.
|
|
829
|
+
|
|
830
|
+
**Start with an empty store.** Bind the store name, then deploy:
|
|
831
|
+
|
|
832
|
+
```sh
|
|
833
|
+
agentbricks memory bind support-agent-memory
|
|
834
|
+
agentbricks deploy my-agent
|
|
835
|
+
```
|
|
836
|
+
|
|
837
|
+
**Start with memories already in the store.** Create the store, add entries, then bind and deploy:
|
|
838
|
+
|
|
839
|
+
```sh
|
|
840
|
+
agentbricks memory stores create --name support-agent-memory # prints a Store ID
|
|
841
|
+
agentbricks memory entries create --store <Store ID> \
|
|
842
|
+
--actor-id you@example.com \
|
|
843
|
+
--path /preferences/style.md \
|
|
844
|
+
--content "Prefers Python and concise answers with code examples."
|
|
845
|
+
agentbricks memory bind support-agent-memory
|
|
846
|
+
agentbricks deploy my-agent
|
|
847
|
+
```
|
|
848
|
+
|
|
849
|
+
`--path` is the entry's key inside the store, written like a file path; it isn't a file on your
|
|
850
|
+
machine. `--actor-id` is the user the memory belongs to. In the deployed chat app, the actor is the
|
|
851
|
+
signed-in user's email, so seed entries under your own email to see them recalled. `--store` takes
|
|
852
|
+
the Store ID that `memory stores create` (or `memory stores list`) prints, while `bind` takes the
|
|
853
|
+
store name. Check what you seeded with
|
|
854
|
+
`agentbricks memory entries list --store <Store ID> --actor-id you@example.com`.
|
|
855
|
+
|
|
767
856
|
### Declaring and provisioning stores
|
|
768
857
|
|
|
769
858
|
For a deployed agent, `agent.toml` declares which stores it uses and `agentbricks deploy` provisions them —
|
|
@@ -785,6 +874,13 @@ agentbricks memory bind support-agent-memory
|
|
|
785
874
|
agentbricks deploy my-agent
|
|
786
875
|
```
|
|
787
876
|
|
|
877
|
+
A store that already exists is reused as is: `deploy` doesn't create a second one or change who else
|
|
878
|
+
can access it. Its only permission change is a WRITE grant for the app's service principal, which
|
|
879
|
+
needs you to be the store's creator or a workspace admin; if you aren't, the deploy still succeeds
|
|
880
|
+
and reports the missing grant. In a shared workspace, give teammates access with
|
|
881
|
+
`agentbricks memory stores permissions grant` (or `agentbricks sessions stores permissions grant`);
|
|
882
|
+
see [Managing store permissions](#managing-store-permissions).
|
|
883
|
+
|
|
788
884
|
Memory and session stores are independent resources: deleting one never affects the other.
|
|
789
885
|
For projects with `agent.toml`, unbinding either store removes its declaration; the next deploy
|
|
790
886
|
removes the corresponding `AGENT_MEMORY_STORE` or `AGENT_SESSION_STORE` entry from `app.yaml`.
|
|
@@ -805,7 +901,7 @@ and declares the Prompt Registry prompts it loads so the search can rewrite them
|
|
|
805
901
|
|
|
806
902
|
```sh
|
|
807
903
|
agentbricks experimental models bind main.my_agent.router_llm --role router --default system.ai.claude-haiku-4-5
|
|
808
|
-
agentbricks experimental models bind main.my_agent.writer_llm --role writer --default system.ai.claude-sonnet-
|
|
904
|
+
agentbricks experimental models bind main.my_agent.writer_llm --role writer --default system.ai.claude-sonnet-5-5
|
|
809
905
|
agentbricks experimental prompts bind main.my_agent.writer
|
|
810
906
|
agentbricks deploy my-agent # creates the services and grants the app access to them and the prompt
|
|
811
907
|
agentbricks experimental models upgrade -c router=claude-haiku-4-5,gpt-5-4-nano -c writer=claude-haiku-4-5 \
|
|
@@ -847,7 +943,7 @@ result = optimize_prompts_and_models(
|
|
|
847
943
|
prompt_uris=["prompts:/main.my_agent.router@production"],
|
|
848
944
|
gateway_endpoints={
|
|
849
945
|
"main.my_agent.router_llm": ["claude-haiku-4-5", "gpt-5-4-mini"],
|
|
850
|
-
"main.my_agent.writer_llm": ["claude-sonnet-
|
|
946
|
+
"main.my_agent.writer_llm": ["claude-sonnet-5-5", "claude-haiku-4-5"],
|
|
851
947
|
},
|
|
852
948
|
scorers=scorers, # MLflow scorers, or (inputs, expectations, answer) -> float
|
|
853
949
|
max_metric_calls=200,
|
|
@@ -1083,7 +1179,7 @@ requests. By default, each App user's `X-Routing-Key` matches its generated user
|
|
|
1083
1179
|
|
|
1084
1180
|
The final summary includes counts, throughput including drain, successful-only and all-completed
|
|
1085
1181
|
latency percentiles, answer-text TTFT, token usage, coverage, incomplete attempts, and generator CPU
|
|
1086
|
-
warnings. With `--output json
|
|
1182
|
+
warnings. With `--output json`, stdout contains one Agent Bricks summary object;
|
|
1087
1183
|
progress stays on stderr. This is the same object saved as `summary.json`.
|
|
1088
1184
|
Locust's rounded histogram buckets are used for percentiles; all-completed timings include failures.
|
|
1089
1185
|
These bounded tests measure the selected workload and do not establish sustainable capacity or answer quality.
|
|
@@ -1272,7 +1368,7 @@ Deploy derives Apps user scopes from explicit `auth = "user"` bindings and union
|
|
|
1272
1368
|
| UC function | `mcp.functions` |
|
|
1273
1369
|
| Sandbox with a Volume downscope | `ai-gateway`, `files` |
|
|
1274
1370
|
| First-class Genie One or Genie Agent | `genie` |
|
|
1275
|
-
| Sandbox with token injection | `ai-gateway`, `workspace.workspace` |
|
|
1371
|
+
| Sandbox with token injection | `ai-gateway`, `workspace.workspace`, `files`, `sql`, `catalog.catalogs:read`, `catalog.schemas:read`, `catalog.tables:read` |
|
|
1276
1372
|
| Sandbox with token injection disabled | `ai-gateway` |
|
|
1277
1373
|
|
|
1278
1374
|
For example, bind Genie tools in a current project with `server = "agentbricks"`:
|
|
@@ -1300,15 +1396,20 @@ The `system.ai.dbsql` managed MCP additionally requests the Apps `sql` user scop
|
|
|
1300
1396
|
API consent, not `sql:restricted-query`; read-only enforcement remains the service policy plus the
|
|
1301
1397
|
requesting user's Unity Catalog grants. DBSQL does not use Databricks Connect.
|
|
1302
1398
|
|
|
1303
|
-
When a user-auth sandbox has `databricks_access_token_included = true`,
|
|
1304
|
-
|
|
1305
|
-
|
|
1306
|
-
|
|
1307
|
-
Unity Catalog
|
|
1308
|
-
|
|
1309
|
-
|
|
1310
|
-
|
|
1311
|
-
the
|
|
1399
|
+
When a user-auth sandbox has `databricks_access_token_included = true`, the injected credential
|
|
1400
|
+
carries only the App's user API scopes, so the sandbox requests `workspace.workspace` (workspace
|
|
1401
|
+
files), `files` (Volume files through the Files API), `sql` (SQL warehouses through the Statement
|
|
1402
|
+
Execution API), and `catalog.catalogs:read`, `catalog.schemas:read`, and `catalog.tables:read`
|
|
1403
|
+
(Unity Catalog metadata). Apps has no user API scope for Databricks Connect, clusters, jobs, or
|
|
1404
|
+
secrets, so sandbox code cannot call those APIs as the request user; use `auth = "app"` for them.
|
|
1405
|
+
An existing App deployed before these defaults needs `--allow-user-scope-update` once. A sandbox
|
|
1406
|
+
binding with a Volume downscope also requests the Apps `files` user scope.
|
|
1407
|
+
OAuth consent does not grant data access: the requesting user still needs the corresponding
|
|
1408
|
+
Unity Catalog and warehouse privileges, and the sandbox downscope remains authoritative. A sandbox
|
|
1409
|
+
binding with token injection disabled requests none of these credential scopes; its other
|
|
1410
|
+
resource-derived scopes still apply. Databricks Apps rejects the legacy bare `workspace` scope, so
|
|
1411
|
+
Agent Bricks requests `workspace.workspace`. These scopes are requested only for `auth = "user"`;
|
|
1412
|
+
`auth = "app"` uses the App service principal's permissions instead.
|
|
1312
1413
|
|
|
1313
1414
|
Review the target App's scopes and coordinate with its other owners before allowing the update. Once
|
|
1314
1415
|
those scopes are present, later deploys do not need the flag. The CLI preserves unrelated scopes,
|
|
@@ -1464,9 +1565,8 @@ agentbricks tools remove genie_agent
|
|
|
1464
1565
|
to `user`; choose `--auth app` deliberately for App service-principal execution. Existing manifests
|
|
1465
1566
|
without `auth` preserve App/default identity. Both add commands and `remove` accept `--source PATH`
|
|
1466
1567
|
to select a project instead of the current directory. Discovery needs no project; read that
|
|
1467
|
-
project's `agent.toml` to inspect configured bindings. For scripted output,
|
|
1468
|
-
|
|
1469
|
-
`agentbricks -o json tools add genie-one --source ./my-agent`. Adding a binding is offline: it updates
|
|
1568
|
+
project's `agent.toml` to inspect configured bindings. For scripted output, add `-o json`, as in
|
|
1569
|
+
`agentbricks tools add genie-one --source ./my-agent -o json`. Adding a binding is offline: it updates
|
|
1470
1570
|
`agent.toml` without contacting Genie or checking permissions. The corresponding sources are:
|
|
1471
1571
|
|
|
1472
1572
|
```toml
|
|
@@ -1537,7 +1637,8 @@ agentbricks --profile <profile> deploy agent-bricks-agent-demo --source .
|
|
|
1537
1637
|
(`bind` declares the store name in `agent.toml`; `agentbricks deploy` creates any declared-but-missing
|
|
1538
1638
|
store and grants the app's service principal access to it. The memory store id flows to the runtime
|
|
1539
1639
|
via the `AGENT_MEMORY_STORE` env var that `deploy` injects; `agentbricks dev` runs locally with memory off
|
|
1540
|
-
and does not inject it
|
|
1640
|
+
and does not inject it, so the chat app shows "Not connected" for memory until you deploy. The id is
|
|
1641
|
+
not persisted in `agent.toml`.)
|
|
1541
1642
|
|
|
1542
1643
|
The chat UI generates a stable application session UUID in browser local storage, sends it as the
|
|
1543
1644
|
invocation's top-level `session_id`, sends the signed-in user as `input.actor`, and creates a fresh
|
|
@@ -121,11 +121,32 @@ credentials.
|
|
|
121
121
|
|
|
122
122
|
If Databricks SDK default authentication is already configured, you can skip `agentbricks login`.
|
|
123
123
|
You can also pass the global `--profile/-p` option before an individual command, for example
|
|
124
|
-
`agentbricks --profile <profile> tools list`. Use `--output json` for
|
|
124
|
+
`agentbricks --profile <profile> tools list`. Use `--output json` (before or after the command) for
|
|
125
|
+
scripting.
|
|
125
126
|
|
|
126
127
|
The CLI sends best effort command usage telemetry after leaf commands. Its log records the static
|
|
127
128
|
command path, package version, operating system, duration, and process outcome (exit code and, for
|
|
128
|
-
nonzero exits, a bounded error category).
|
|
129
|
+
nonzero exits, a bounded error category). Failures can also include up to 4096 UTF-8 bytes of
|
|
130
|
+
error text in `failure_message`. Error text includes exception messages and fully captured
|
|
131
|
+
failed subprocess output, with recognized credentials, paths, and email addresses scrubbed.
|
|
132
|
+
Combined failure text over 65,536 characters is also omitted before scrubbing.
|
|
133
|
+
Credential assignments, auth headers, credential options, and encoded text cause the remaining
|
|
134
|
+
captured text to be omitted; preceding diagnostic text is retained. This avoids parsing arbitrary
|
|
135
|
+
JSON, YAML, or Python values. Recognizable standalone tokens and private keys are also masked.
|
|
136
|
+
This follows the Asset Bundles minimization pattern and is best effort; other customer content
|
|
137
|
+
may remain in service responses or application output.
|
|
138
|
+
It is labeled `DATA_LABEL_USER_COMMANDS_RESPONSE`, excluded from centralized logfood, and retained
|
|
139
|
+
regionally only where customer logging and encryption policies permit. Error text is omitted for
|
|
140
|
+
parser errors and interruptions. Collection requires Legal approval and schema deployment.
|
|
141
|
+
For `dev`, failure text can include complete child output up to 3072 bytes per captured stream.
|
|
142
|
+
Once a stream exceeds that limit, all its retained text is permanently discarded and replaced with
|
|
143
|
+
`[REDACTED]`, including later plain error messages, because partial output may have lost credential
|
|
144
|
+
context. Short complete output is scrubbed before upload, including private keys. Displayed child
|
|
145
|
+
output is unchanged. With one output stream redirected, the terminal stream is inherited unchanged
|
|
146
|
+
and only the redirected stream is retained. When both streams point to the same regular file, both
|
|
147
|
+
are inherited without capture to preserve their original offsets and redirection behavior.
|
|
148
|
+
Startup milestones remain internal; a killed process or unavailable upload can still leave no event.
|
|
149
|
+
Parameter entries include explicitly supplied options
|
|
129
150
|
and parsed Click defaults with supported typed values, automatically across all commands and
|
|
130
151
|
parent groups. Declare defaults in Click options so the shared emitter can read the resolved
|
|
131
152
|
values; fallbacks applied only inside command callbacks are not visible to Click. Omitted free-form
|
|
@@ -135,9 +156,8 @@ choices contribute an `AGENTBRICKS_CLI_`-prefixed value. Click boolean and numer
|
|
|
135
156
|
contribute their typed values; explicitly supplied non-finite floats and integers outside the log
|
|
136
157
|
schema's 64-bit range remain presence-only, while unsupported defaults are omitted. Hidden and
|
|
137
158
|
deprecated options follow the same policy, and repeated
|
|
138
|
-
options contribute one parameter entry per supplied value, up to 64 entries.
|
|
139
|
-
raw command arguments, paths, IDs,
|
|
140
|
-
messages are omitted. Set
|
|
159
|
+
options contribute one parameter entry per supplied value, up to 64 entries. Parameter telemetry
|
|
160
|
+
omits positional arguments, raw command arguments, paths, IDs, and arbitrary free-form values. Set
|
|
141
161
|
`AGENTBRICKS_DISABLE_TELEMETRY=1` to disable these uploads.
|
|
142
162
|
|
|
143
163
|
Telemetry runs only when a leaf command is invoked, whether its callback succeeds or fails. Help
|
|
@@ -150,6 +170,25 @@ thread, returning sooner if the worker finishes. This is not a delivery guarante
|
|
|
150
170
|
uploads can be lost when the process exits after the allowance expires. Missing credentials or a
|
|
151
171
|
failed upload never change the command result.
|
|
152
172
|
|
|
173
|
+
Deploy and `deployments wait` telemetry includes a random invocation UUID, whether a gated
|
|
174
|
+
agent-details link was printed, the observed deployment state, and whether the process is an
|
|
175
|
+
internal background child. Details links carry the invocation UUID so browser arrivals can be
|
|
176
|
+
joined to the command that printed them. The UUID contains no agent name or authentication data.
|
|
177
|
+
Rollout outcomes are recorded independently of link availability, including failed rollouts;
|
|
178
|
+
preparation failures leave the deployment outcome unspecified.
|
|
179
|
+
`AGENTBRICKS_DISABLE_TELEMETRY=1` also removes these attribution parameters while keeping the link.
|
|
180
|
+
`deployments get` and `deployments list` also attach a per-command UUID to details links.
|
|
181
|
+
All rows from one list share one UUID and one command event; their deployment outcome stays
|
|
182
|
+
unspecified because these commands only read state. List links count as emitted only when JSON
|
|
183
|
+
output or terminal hyperlink rendering preserves their targets. Plain redirected output and
|
|
184
|
+
terminal modes that strip hyperlink targets keep `details_link_emitted=false`; use `--output json`
|
|
185
|
+
to capture the URLs. Group arrivals by the joined event's
|
|
186
|
+
`command_path` to distinguish deploy, wait, get, and list. Count distinct invocation IDs, rather
|
|
187
|
+
than list rows or repeated page loads, for command conversion percentages.
|
|
188
|
+
A wait command has its own invocation ID; it is not another deploy. Exclude background children
|
|
189
|
+
from user-invoked command counts. Link arrivals measure browser opens, including copied links,
|
|
190
|
+
not terminal mouse clicks or proof that the deployer and viewer are the same person.
|
|
191
|
+
|
|
153
192
|
## Quickstart
|
|
154
193
|
|
|
155
194
|
The shortest path from a blank directory to a running and deployed agent:
|
|
@@ -165,6 +204,12 @@ agentbricks deploy # deploy to Databricks as agent-bricks-my-agent
|
|
|
165
204
|
`agentbricks dev` runs the agent locally on `http://localhost:8000`, wrapping the Databricks Apps
|
|
166
205
|
local runtime so local behavior matches a deployment.
|
|
167
206
|
|
|
207
|
+
Memory and session stores are off by default in `agentbricks dev`, even when a store is bound in
|
|
208
|
+
`agent.toml`: the chat app shows "Not connected" for memory, and conversation state stays in
|
|
209
|
+
process. They connect after `agentbricks deploy`. To use real stores locally, set
|
|
210
|
+
`AGENT_MEMORY_STORE` (the Store ID) and `AGENT_SESSION_STORE` (the store name) in the project's
|
|
211
|
+
`.env`.
|
|
212
|
+
|
|
168
213
|
`agentbricks init` records the deployment name in `agent.toml`, so `agentbricks deploy` from the
|
|
169
214
|
project directory deploys a Databricks App named `agent-bricks-my-agent`, provisions the
|
|
170
215
|
stores declared in `agent.toml`, and grants the app's service principal access to the stores and
|
|
@@ -179,6 +224,18 @@ The app's compute starts first and boots while the other resources are provision
|
|
|
179
224
|
deploy stops partway, the app it created is kept: re-run `agentbricks deploy` to resume, or remove
|
|
180
225
|
it with `agentbricks deployments delete agent-bricks-my-agent`.
|
|
181
226
|
|
|
227
|
+
When the workspace has both the Agent Memory Sessions beta and the new Agents UI enabled,
|
|
228
|
+
deploy output also includes an **Agent details** link to the workspace management page. This
|
|
229
|
+
applies to first deploys, redeploys, `--no-wait`, and `deployments wait`.
|
|
230
|
+
`deployments get` shows the same link alongside the app URL; `deployments list` links agent
|
|
231
|
+
names to their details pages and keeps a separate **Open app** link. JSON output adds
|
|
232
|
+
`details_url` when available and retains `url` for the deployed agent. The optional flag lookup
|
|
233
|
+
waits at most two seconds per command, including lists; unavailable or disabled flags omit the
|
|
234
|
+
link without affecting the command.
|
|
235
|
+
When following a local deploy record, `deployments wait` also requires its recorded workspace
|
|
236
|
+
host and ID to match the selected profile. Older records or records without a workspace ID omit
|
|
237
|
+
the management link; the recorded deployment status and invocation URL are still available.
|
|
238
|
+
|
|
182
239
|
### Deploying from a coding agent
|
|
183
240
|
|
|
184
241
|
A first deploy takes ~3 min (mostly starting app compute); redeploys are faster. Either run
|
|
@@ -627,8 +684,9 @@ it in `recall` and `list_memories`. `memory_tools` resolves the store from the `
|
|
|
627
684
|
binding, carried to the runtime by the `AGENT_MEMORY_STORE` env var that `agentbricks deploy`
|
|
628
685
|
injects, and returns no tools when no store is set, so the agent runs unchanged.
|
|
629
686
|
That "no store set" path is also how it runs under `agentbricks dev`, which runs locally: memory is off
|
|
630
|
-
there (the store is provisioned and used only at deploy)
|
|
631
|
-
|
|
687
|
+
by default there (the store is provisioned and used only at deploy), even when a store is bound in
|
|
688
|
+
`agent.toml`. Setting `AGENT_MEMORY_STORE` in the project's `.env` uses that store locally. The
|
|
689
|
+
OpenAI Agents adapter exposes the same tools as `databricks_agentkit.openai.memory_tools(actor)`:
|
|
632
690
|
|
|
633
691
|
```python
|
|
634
692
|
from databricks_agentkit.langgraph import memory_tools
|
|
@@ -665,8 +723,8 @@ agentbricks memory stores permissions revoke memory-stores/<id> \
|
|
|
665
723
|
|
|
666
724
|
Session stores accept their configured name or `session-stores/<name>`. Memory stores accept an ID
|
|
667
725
|
or `memory-stores/<id>`; permission Get also accepts the display-name lookup supported by store Get
|
|
668
|
-
and rejects ambiguous matches. The global `--profile`
|
|
669
|
-
`
|
|
726
|
+
and rejects ambiguous matches. The global `--profile` option goes before `sessions` or `memory`;
|
|
727
|
+
`--output json` goes before or after the command. List follows the existing CLI pagination convention: one JSON/piped page
|
|
670
728
|
with `next_page_token`, interactive text pages, or every page with `--all`.
|
|
671
729
|
|
|
672
730
|
Get always returns the authenticated caller's effective permission, including
|
|
@@ -711,8 +769,8 @@ trusted application context. The chat app sends the signed-in user; HTTP clients
|
|
|
711
769
|
`agentbricks endpoint invoke`, have to send it themselves. With a request-user (`auth = "user"`) tool
|
|
712
770
|
bound, the runtime also namespaces a supplied `actor` to the signed-in user.
|
|
713
771
|
|
|
714
|
-
Memory is off under `agentbricks dev`, so try this against a deployed agent: two
|
|
715
|
-
actor.
|
|
772
|
+
Memory is off by default under `agentbricks dev`, so try this against a deployed agent: two
|
|
773
|
+
conversations, one actor.
|
|
716
774
|
|
|
717
775
|
```sh
|
|
718
776
|
ask() { agentbricks --profile <profile> endpoint invoke agent-bricks-my-agent --path /api/invocations \
|
|
@@ -721,6 +779,37 @@ ask "Remember that I prefer answers as bullet points." # conversation 1 saves a
|
|
|
721
779
|
ask "How do I like my answers formatted?" # conversation 2 recalls it
|
|
722
780
|
```
|
|
723
781
|
|
|
782
|
+
### Seeding and using memory from the CLI
|
|
783
|
+
|
|
784
|
+
There are two ways to get a memory store behind a deployed agent. Both end with
|
|
785
|
+
`agentbricks deploy`, which creates the store if it doesn't exist and grants the app access to it.
|
|
786
|
+
|
|
787
|
+
**Start with an empty store.** Bind the store name, then deploy:
|
|
788
|
+
|
|
789
|
+
```sh
|
|
790
|
+
agentbricks memory bind support-agent-memory
|
|
791
|
+
agentbricks deploy my-agent
|
|
792
|
+
```
|
|
793
|
+
|
|
794
|
+
**Start with memories already in the store.** Create the store, add entries, then bind and deploy:
|
|
795
|
+
|
|
796
|
+
```sh
|
|
797
|
+
agentbricks memory stores create --name support-agent-memory # prints a Store ID
|
|
798
|
+
agentbricks memory entries create --store <Store ID> \
|
|
799
|
+
--actor-id you@example.com \
|
|
800
|
+
--path /preferences/style.md \
|
|
801
|
+
--content "Prefers Python and concise answers with code examples."
|
|
802
|
+
agentbricks memory bind support-agent-memory
|
|
803
|
+
agentbricks deploy my-agent
|
|
804
|
+
```
|
|
805
|
+
|
|
806
|
+
`--path` is the entry's key inside the store, written like a file path; it isn't a file on your
|
|
807
|
+
machine. `--actor-id` is the user the memory belongs to. In the deployed chat app, the actor is the
|
|
808
|
+
signed-in user's email, so seed entries under your own email to see them recalled. `--store` takes
|
|
809
|
+
the Store ID that `memory stores create` (or `memory stores list`) prints, while `bind` takes the
|
|
810
|
+
store name. Check what you seeded with
|
|
811
|
+
`agentbricks memory entries list --store <Store ID> --actor-id you@example.com`.
|
|
812
|
+
|
|
724
813
|
### Declaring and provisioning stores
|
|
725
814
|
|
|
726
815
|
For a deployed agent, `agent.toml` declares which stores it uses and `agentbricks deploy` provisions them —
|
|
@@ -742,6 +831,13 @@ agentbricks memory bind support-agent-memory
|
|
|
742
831
|
agentbricks deploy my-agent
|
|
743
832
|
```
|
|
744
833
|
|
|
834
|
+
A store that already exists is reused as is: `deploy` doesn't create a second one or change who else
|
|
835
|
+
can access it. Its only permission change is a WRITE grant for the app's service principal, which
|
|
836
|
+
needs you to be the store's creator or a workspace admin; if you aren't, the deploy still succeeds
|
|
837
|
+
and reports the missing grant. In a shared workspace, give teammates access with
|
|
838
|
+
`agentbricks memory stores permissions grant` (or `agentbricks sessions stores permissions grant`);
|
|
839
|
+
see [Managing store permissions](#managing-store-permissions).
|
|
840
|
+
|
|
745
841
|
Memory and session stores are independent resources: deleting one never affects the other.
|
|
746
842
|
For projects with `agent.toml`, unbinding either store removes its declaration; the next deploy
|
|
747
843
|
removes the corresponding `AGENT_MEMORY_STORE` or `AGENT_SESSION_STORE` entry from `app.yaml`.
|
|
@@ -762,7 +858,7 @@ and declares the Prompt Registry prompts it loads so the search can rewrite them
|
|
|
762
858
|
|
|
763
859
|
```sh
|
|
764
860
|
agentbricks experimental models bind main.my_agent.router_llm --role router --default system.ai.claude-haiku-4-5
|
|
765
|
-
agentbricks experimental models bind main.my_agent.writer_llm --role writer --default system.ai.claude-sonnet-
|
|
861
|
+
agentbricks experimental models bind main.my_agent.writer_llm --role writer --default system.ai.claude-sonnet-5-5
|
|
766
862
|
agentbricks experimental prompts bind main.my_agent.writer
|
|
767
863
|
agentbricks deploy my-agent # creates the services and grants the app access to them and the prompt
|
|
768
864
|
agentbricks experimental models upgrade -c router=claude-haiku-4-5,gpt-5-4-nano -c writer=claude-haiku-4-5 \
|
|
@@ -804,7 +900,7 @@ result = optimize_prompts_and_models(
|
|
|
804
900
|
prompt_uris=["prompts:/main.my_agent.router@production"],
|
|
805
901
|
gateway_endpoints={
|
|
806
902
|
"main.my_agent.router_llm": ["claude-haiku-4-5", "gpt-5-4-mini"],
|
|
807
|
-
"main.my_agent.writer_llm": ["claude-sonnet-
|
|
903
|
+
"main.my_agent.writer_llm": ["claude-sonnet-5-5", "claude-haiku-4-5"],
|
|
808
904
|
},
|
|
809
905
|
scorers=scorers, # MLflow scorers, or (inputs, expectations, answer) -> float
|
|
810
906
|
max_metric_calls=200,
|
|
@@ -1040,7 +1136,7 @@ requests. By default, each App user's `X-Routing-Key` matches its generated user
|
|
|
1040
1136
|
|
|
1041
1137
|
The final summary includes counts, throughput including drain, successful-only and all-completed
|
|
1042
1138
|
latency percentiles, answer-text TTFT, token usage, coverage, incomplete attempts, and generator CPU
|
|
1043
|
-
warnings. With `--output json
|
|
1139
|
+
warnings. With `--output json`, stdout contains one Agent Bricks summary object;
|
|
1044
1140
|
progress stays on stderr. This is the same object saved as `summary.json`.
|
|
1045
1141
|
Locust's rounded histogram buckets are used for percentiles; all-completed timings include failures.
|
|
1046
1142
|
These bounded tests measure the selected workload and do not establish sustainable capacity or answer quality.
|
|
@@ -1229,7 +1325,7 @@ Deploy derives Apps user scopes from explicit `auth = "user"` bindings and union
|
|
|
1229
1325
|
| UC function | `mcp.functions` |
|
|
1230
1326
|
| Sandbox with a Volume downscope | `ai-gateway`, `files` |
|
|
1231
1327
|
| First-class Genie One or Genie Agent | `genie` |
|
|
1232
|
-
| Sandbox with token injection | `ai-gateway`, `workspace.workspace` |
|
|
1328
|
+
| Sandbox with token injection | `ai-gateway`, `workspace.workspace`, `files`, `sql`, `catalog.catalogs:read`, `catalog.schemas:read`, `catalog.tables:read` |
|
|
1233
1329
|
| Sandbox with token injection disabled | `ai-gateway` |
|
|
1234
1330
|
|
|
1235
1331
|
For example, bind Genie tools in a current project with `server = "agentbricks"`:
|
|
@@ -1257,15 +1353,20 @@ The `system.ai.dbsql` managed MCP additionally requests the Apps `sql` user scop
|
|
|
1257
1353
|
API consent, not `sql:restricted-query`; read-only enforcement remains the service policy plus the
|
|
1258
1354
|
requesting user's Unity Catalog grants. DBSQL does not use Databricks Connect.
|
|
1259
1355
|
|
|
1260
|
-
When a user-auth sandbox has `databricks_access_token_included = true`,
|
|
1261
|
-
|
|
1262
|
-
|
|
1263
|
-
|
|
1264
|
-
Unity Catalog
|
|
1265
|
-
|
|
1266
|
-
|
|
1267
|
-
|
|
1268
|
-
the
|
|
1356
|
+
When a user-auth sandbox has `databricks_access_token_included = true`, the injected credential
|
|
1357
|
+
carries only the App's user API scopes, so the sandbox requests `workspace.workspace` (workspace
|
|
1358
|
+
files), `files` (Volume files through the Files API), `sql` (SQL warehouses through the Statement
|
|
1359
|
+
Execution API), and `catalog.catalogs:read`, `catalog.schemas:read`, and `catalog.tables:read`
|
|
1360
|
+
(Unity Catalog metadata). Apps has no user API scope for Databricks Connect, clusters, jobs, or
|
|
1361
|
+
secrets, so sandbox code cannot call those APIs as the request user; use `auth = "app"` for them.
|
|
1362
|
+
An existing App deployed before these defaults needs `--allow-user-scope-update` once. A sandbox
|
|
1363
|
+
binding with a Volume downscope also requests the Apps `files` user scope.
|
|
1364
|
+
OAuth consent does not grant data access: the requesting user still needs the corresponding
|
|
1365
|
+
Unity Catalog and warehouse privileges, and the sandbox downscope remains authoritative. A sandbox
|
|
1366
|
+
binding with token injection disabled requests none of these credential scopes; its other
|
|
1367
|
+
resource-derived scopes still apply. Databricks Apps rejects the legacy bare `workspace` scope, so
|
|
1368
|
+
Agent Bricks requests `workspace.workspace`. These scopes are requested only for `auth = "user"`;
|
|
1369
|
+
`auth = "app"` uses the App service principal's permissions instead.
|
|
1269
1370
|
|
|
1270
1371
|
Review the target App's scopes and coordinate with its other owners before allowing the update. Once
|
|
1271
1372
|
those scopes are present, later deploys do not need the flag. The CLI preserves unrelated scopes,
|
|
@@ -1421,9 +1522,8 @@ agentbricks tools remove genie_agent
|
|
|
1421
1522
|
to `user`; choose `--auth app` deliberately for App service-principal execution. Existing manifests
|
|
1422
1523
|
without `auth` preserve App/default identity. Both add commands and `remove` accept `--source PATH`
|
|
1423
1524
|
to select a project instead of the current directory. Discovery needs no project; read that
|
|
1424
|
-
project's `agent.toml` to inspect configured bindings. For scripted output,
|
|
1425
|
-
|
|
1426
|
-
`agentbricks -o json tools add genie-one --source ./my-agent`. Adding a binding is offline: it updates
|
|
1525
|
+
project's `agent.toml` to inspect configured bindings. For scripted output, add `-o json`, as in
|
|
1526
|
+
`agentbricks tools add genie-one --source ./my-agent -o json`. Adding a binding is offline: it updates
|
|
1427
1527
|
`agent.toml` without contacting Genie or checking permissions. The corresponding sources are:
|
|
1428
1528
|
|
|
1429
1529
|
```toml
|
|
@@ -1494,7 +1594,8 @@ agentbricks --profile <profile> deploy agent-bricks-agent-demo --source .
|
|
|
1494
1594
|
(`bind` declares the store name in `agent.toml`; `agentbricks deploy` creates any declared-but-missing
|
|
1495
1595
|
store and grants the app's service principal access to it. The memory store id flows to the runtime
|
|
1496
1596
|
via the `AGENT_MEMORY_STORE` env var that `deploy` injects; `agentbricks dev` runs locally with memory off
|
|
1497
|
-
and does not inject it
|
|
1597
|
+
and does not inject it, so the chat app shows "Not connected" for memory until you deploy. The id is
|
|
1598
|
+
not persisted in `agent.toml`.)
|
|
1498
1599
|
|
|
1499
1600
|
The chat UI generates a stable application session UUID in browser local storage, sends it as the
|
|
1500
1601
|
invocation's top-level `session_id`, sends the signed-in user as `input.actor`, and creates a fresh
|
{databricks_agentbricks-0.8.0 → databricks_agentbricks-0.10.0}/src/databricks_agentbricks/cli/app.py
RENAMED
|
@@ -123,9 +123,9 @@ def _emit_trailing_spacer() -> None:
|
|
|
123
123
|
try:
|
|
124
124
|
# Suppress under `-o json` even on a (pseudo-)TTY — a machine may be parsing stdout under
|
|
125
125
|
# `docker run -t` / `script` / a CI PTY, where isatty() alone would wrongly allow the
|
|
126
|
-
# spacer. `errors.
|
|
127
|
-
# way by render.py), so it's still available here after the Click context is torn down.
|
|
128
|
-
if errors.
|
|
126
|
+
# spacer. `errors.error_output_mode()` is a process global (set by the root group, read the
|
|
127
|
+
# same way by render.py), so it's still available here after the Click context is torn down.
|
|
128
|
+
if errors.error_output_mode() == "json" or not sys.stdout.isatty():
|
|
129
129
|
return
|
|
130
130
|
click.echo()
|
|
131
131
|
except Exception:
|