@dbx-tools/cli
Use one CLI to authenticate with Databricks, connect local PostgreSQL tools to Lakebase, serve Databricks models to coding agents, run graph memory, and share applications through a gated public URL.
Install And Connect
Section titled “Install And Connect”bun add --global @dbx-tools/clidbx-tools is an alias for dbx. Authentication and a configured Databricks
profile are resolved automatically. Pass --profile only to override that
selection; examples that use MY-PROFILE show the explicit form.
Serve Models To Local Tools
Section titled “Serve Models To Local Tools”dbx model-gateway --profile MY-PROFILE --port 4000Point an OpenAI-compatible client at http://127.0.0.1:4000/v1. The generated
command reference includes all gateway and desktop-service options.
Requests may omit model to select the best available chat endpoint. Set a
gateway default with --model or --model-class, or select a class per request
with the x-dbx-tools-model-class header.
Run Genie Code
Section titled “Run Genie Code”dbx genie runs the Databricks Genie Code CLI with dbx-tools model discovery,
authentication, and configuration. It removes the setup steps normally required
before the first non-interactive Genie command:
- No Genie onboarding or separate
genieinitialization. - No Genie configuration profile to create or pass.
- No manual provider URL, token command, workspace header, or
config.toml. - No required
--profilewhen dbx-tools can discover a configured Databricks profile automatically. - No restriction to Genie Code’s default model. Select any compatible model available in the workspace, including GPT, Grok, Claude, Gemini, and custom serving endpoints.
With no model option, dbx-tools selects the best available tool-capable chat
model. Use either --model for fuzzy or exact model selection, or
--model-class for a capability band:
# Select the best available chat model.dbx genie
# Select the best fast chat model.dbx genie --model-class chat-fast
# Select the best matching GPT model.dbx genie --model gpt
# Select another model family.dbx genie --model grok
# Pin an exact model or serving endpoint.dbx genie --profile MY-PROFILE --model databricks-gpt-5-6-soldbx-genie is the equivalent installed binary:
dbx-genie --model gptThe command installs the pinned Genie Code package under ~/.dbx-tools and
creates one persistent home per exact Databricks profile. Models share that
home’s conversation state and project trust, while each invocation receives a
model-specific overlay with an independent local gateway port and credential.
Unknown flags, prompts, and extra arguments are forwarded to Genie Code:
dbx genie --model gpt "Summarize the changes since the latest release."dbx genie --model claude -- exec --ephemeral "Review this repository."Use -- only when a wrapper option such as --model must be sent to Genie
instead of being consumed by dbx genie.
Connect To Lakebase
Section titled “Connect To Lakebase”dbx lakebase-proxy --profile MY-PROFILE --port 5432Connect your PostgreSQL client to the loopback listener. The command reference includes target selection, connection URLs, and service commands.
Add Memory Or Share An App
Section titled “Add Memory Or Share An App”dbx graphiti --profile MY-PROFILEdbx tunnel --allow example.com -- bun src/server.tsgraphiti provides graph memory for agents. tunnel adds a public URL with
passwordless access to an existing process.
Export AppKit Configuration
Section titled “Export AppKit Configuration”eval "$(dbx appkit env --quiet)"Use the resolved AppKit environment before starting another process. The AppKit and authentication command groups below include JSON, Windows, and token options.
Bootstrap A Workspace
Section titled “Bootstrap A Workspace”dbx dev syncIn an empty folder, this creates and initializes a Bun/Projen workspace. In a
cloned workspace, it installs missing tooling before running the requested task.
Arguments after dev are forwarded to Projen.
Once the workspace is initialized, use its tasks directly:
bun run syncbun run sync -- --watchbun run barrelsSee @dbx-tools/projen for workspace configuration and
generation. Command implementations are available from @dbx-tools/cli/appkit,
/auth, /genie, /graphiti, /lakebase-proxy, /model-gateway, and
/tunnel when a Node caller needs to embed one parser.
Command Reference
Section titled “Command Reference”Databricks developer tools: workspace lifecycle, AppKit env, auth, tunnels, and local proxies
dbx [command]Commands
Section titled “Commands”| Command | Description |
|---|---|
dev [projenArgs...] |
Bootstrap or repair a dbx-tools workspace, then forward to projen |
appkit |
AppKit helpers: resolve the environment an AppKit app would start with. |
auth [options] |
Authenticate to Databricks with user or machine OAuth |
tunnel [options] [command...] |
Front a command with a public tunnel and passwordless auth |
lakebase-proxy [options] |
Run a loopback PostgreSQL proxy for Databricks Lakebase |
model-gateway [options] |
Run or manage the AppKit Databricks model gateway |
genie [options] [genieArgs...] |
Run Genie Code through an authenticated local Databricks model gateway |
graphiti [options] |
Run Graphiti or manage its current-user desktop service |
dbx dev
Section titled “dbx dev”Bootstrap or repair a dbx-tools workspace, then forward to projen
dbx dev [projenArgs...]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
projenArgs |
projen task and arguments (e.g. sync –watch) |
dbx appkit
Section titled “dbx appkit”AppKit helpers: resolve the environment an AppKit app would start with.
dbx appkit [command]Commands
Section titled “Commands”| Command | Description |
|---|---|
env [options] |
Run AppKit auto-config and print new/changed env vars. |
dbx appkit env
Section titled “dbx appkit env”Run AppKit auto-config and print new/changed env vars.
dbx appkit env [options]Options
Section titled “Options”| Option | Description |
|---|---|
-f, --format <value> |
Output format: export, windows, or json. (choices: “export”, “windows”, “json”, default: “export”, env: FORMAT) |
-q, --quiet |
Suppress auto-config log output. (default: false, env: QUIET) |
--no-quiet |
Disable suppress auto-config log output. |
dbx auth
Section titled “dbx auth”Authenticate to Databricks with user or machine OAuth
dbx auth [options] [command]Options
Section titled “Options”| Option | Description |
|---|---|
--profile <value> |
Databricks CLI profile. (env: DATABRICKS_CONFIG_PROFILE) |
-s, --scopes <value> |
OAuth scopes. (default: [], env: SCOPES) |
-t, --target <value> |
OAuth target. (choices: “workspace”, “account”, “unified”, env: TARGET) |
--lock-timeout-ms <value> |
Credential lock timeout in milliseconds. (default: 0, env: LOCK_TIMEOUT_MS) |
--login-timeout-ms <value> |
Browser login timeout in milliseconds. (default: 900000, env: LOGIN_TIMEOUT_MS) |
-r, --refresh-buffer-ms <value> |
Token refresh buffer in milliseconds. (default: 300000, env: REFRESH_BUFFER_MS) |
--prefer-user-to-machine |
Prefer a matching user profile over selected machine credentials. (default: true, env: PREFER_USER_TO_MACHINE) |
--no-prefer-user-to-machine |
Disable prefer a matching user profile over selected machine credentials. |
Commands
Section titled “Commands”| Command | Description |
|---|---|
login |
Force browser login and return an access token |
token [options] |
Return a valid access token, logging in when needed |
headers |
Return current Databricks authentication headers |
profile |
Print the configured or automatically detected profile |
logout |
Delete the stored credential for the selected profile |
status |
Show the resolved authentication client configuration |
dbx auth login
Section titled “dbx auth login”Force browser login and return an access token
dbx auth logindbx auth token
Section titled “dbx auth token”Return a valid access token, logging in when needed
dbx auth token [options]Options
Section titled “Options”| Option | Description |
|---|---|
--force-refresh |
Refresh the token before returning it. (default: false, env: FORCE_REFRESH) |
--no-force-refresh |
Disable refresh the token before returning it. |
-l, --login |
Log in when credentials are missing or invalid. (default: true, env: LOGIN) |
--no-login |
Disable log in when credentials are missing or invalid. |
--format <value> |
Output structured token metadata or only the access token. (choices: “json”, “text”, default: “json”, env: FORMAT) |
dbx auth headers
Section titled “dbx auth headers”Return current Databricks authentication headers
dbx auth headersdbx auth profile
Section titled “dbx auth profile”Print the configured or automatically detected profile
dbx auth profiledbx auth logout
Section titled “dbx auth logout”Delete the stored credential for the selected profile
dbx auth logoutdbx auth status
Section titled “dbx auth status”Show the resolved authentication client configuration
dbx auth statusdbx tunnel
Section titled “dbx tunnel”Front a command with a public tunnel and passwordless auth
dbx tunnel [options] [command] [command...]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
command |
the command to wrap, after -- |
Options
Section titled “Options”| Option | Description |
|---|---|
-t, --transport <value> |
Public tunnel transport. (choices: “portr”, “frp”, “both”, env: TUNNEL_TRANSPORT) |
--public-domain <value> |
Public tunnel domain. (env: TUNNEL_PUBLIC_DOMAIN) |
--subdomain <value> |
Portr subdomain. (env: SUBDOMAIN) |
--port <value> |
Public listener port. (env: DATABRICKS_APP_PORT) |
--app-port <value> |
Private wrapped application port. (env: TUNNEL_APP_PORT) |
--allow <value> |
Email allow-list patterns. (env: TUNNEL_AUTH_ALLOW) |
--subject <value> |
Verification email subject. (env: TUNNEL_AUTH_SUBJECT) |
--brand-name <value> |
Verification email brand name. (env: TUNNEL_AUTH_BRAND_NAME) |
-m, --message <value> |
Verification email message. (env: TUNNEL_AUTH_MESSAGE) |
--session-ttl-seconds <value> |
Session lifetime in seconds. (env: TUNNEL_AUTH_SESSION_TTL) |
-c, --code-ttl-seconds <value> |
One-time-code lifetime in seconds. (env: TUNNEL_AUTH_CODE_TTL) |
--session-cutoff <value> |
Invalidate sessions issued before this value. (env: TUNNEL_AUTH_SESSION_CUTOFF) |
--storage <value> |
Authentication database mode. (choices: “auto”, “lakebase”, “sqlite”, env: TUNNEL_AUTH_STORAGE) |
--sqlite-path <value> |
Local authentication SQLite file. (env: TUNNEL_AUTH_SQLITE_PATH) |
--forward-headers <value> |
Additional forwarded request header patterns. (env: TUNNEL_FORWARD_HEADERS) |
-g, --gate-paths <value> |
Additional path prefixes requiring authentication. (env: TUNNEL_GATE_PATHS) |
--bind-hosts <value> |
Interface IPs the gate listens on. (env: BIND_HOSTS) |
-i, --insecure |
Run without an authentication gate. (env: TUNNEL_INSECURE) |
--no-insecure |
Disable run without an authentication gate. |
--frp-server <value> |
FRP control host. (env: FRP_SERVER) |
--frp-public-domain <value> |
FRP public HTTP domain. (env: TUNNEL_FRP_PUBLIC_DOMAIN) |
--frp-server-port <value> |
FRP control port. (env: FRP_SERVER_PORT) |
--frp-protocol <value> |
FRP transport protocol. (env: FRP_PROTOCOL) |
--frp-token <value> |
FRP authentication token. (env: FRP_TOKEN) |
--frp-proxy-name <value> |
FRP proxy registration name. (env: FRP_PROXY_NAME) |
Commands
Section titled “Commands”| Command | Description |
|---|---|
run [options] <command...> |
Wrap a command (the default action) |
status [options] |
Resolve the configuration and print it |
install [transport] |
Install public tunnel client binaries and exit |
dbx tunnel run
Section titled “dbx tunnel run”Wrap a command (the default action)
dbx tunnel run [options] <command...>Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
command |
the command to wrap, after -- |
Options
Section titled “Options”| Option | Description |
|---|---|
-t, --transport <value> |
Public tunnel transport. (choices: “portr”, “frp”, “both”, env: TUNNEL_TRANSPORT) |
--public-domain <value> |
Public tunnel domain. (env: TUNNEL_PUBLIC_DOMAIN) |
--subdomain <value> |
Portr subdomain. (env: SUBDOMAIN) |
--port <value> |
Public listener port. (env: DATABRICKS_APP_PORT) |
--app-port <value> |
Private wrapped application port. (env: TUNNEL_APP_PORT) |
--allow <value> |
Email allow-list patterns. (env: TUNNEL_AUTH_ALLOW) |
--subject <value> |
Verification email subject. (env: TUNNEL_AUTH_SUBJECT) |
--brand-name <value> |
Verification email brand name. (env: TUNNEL_AUTH_BRAND_NAME) |
-m, --message <value> |
Verification email message. (env: TUNNEL_AUTH_MESSAGE) |
--session-ttl-seconds <value> |
Session lifetime in seconds. (env: TUNNEL_AUTH_SESSION_TTL) |
-c, --code-ttl-seconds <value> |
One-time-code lifetime in seconds. (env: TUNNEL_AUTH_CODE_TTL) |
--session-cutoff <value> |
Invalidate sessions issued before this value. (env: TUNNEL_AUTH_SESSION_CUTOFF) |
--storage <value> |
Authentication database mode. (choices: “auto”, “lakebase”, “sqlite”, env: TUNNEL_AUTH_STORAGE) |
--sqlite-path <value> |
Local authentication SQLite file. (env: TUNNEL_AUTH_SQLITE_PATH) |
--forward-headers <value> |
Additional forwarded request header patterns. (env: TUNNEL_FORWARD_HEADERS) |
-g, --gate-paths <value> |
Additional path prefixes requiring authentication. (env: TUNNEL_GATE_PATHS) |
--bind-hosts <value> |
Interface IPs the gate listens on. (env: BIND_HOSTS) |
-i, --insecure |
Run without an authentication gate. (env: TUNNEL_INSECURE) |
--no-insecure |
Disable run without an authentication gate. |
--frp-server <value> |
FRP control host. (env: FRP_SERVER) |
--frp-public-domain <value> |
FRP public HTTP domain. (env: TUNNEL_FRP_PUBLIC_DOMAIN) |
--frp-server-port <value> |
FRP control port. (env: FRP_SERVER_PORT) |
--frp-protocol <value> |
FRP transport protocol. (env: FRP_PROTOCOL) |
--frp-token <value> |
FRP authentication token. (env: FRP_TOKEN) |
--frp-proxy-name <value> |
FRP proxy registration name. (env: FRP_PROXY_NAME) |
dbx tunnel status
Section titled “dbx tunnel status”Resolve the configuration and print it
dbx tunnel status [options]Options
Section titled “Options”| Option | Description |
|---|---|
-t, --transport <value> |
Public tunnel transport. (choices: “portr”, “frp”, “both”, env: TUNNEL_TRANSPORT) |
--public-domain <value> |
Public tunnel domain. (env: TUNNEL_PUBLIC_DOMAIN) |
--subdomain <value> |
Portr subdomain. (env: SUBDOMAIN) |
--port <value> |
Public listener port. (env: DATABRICKS_APP_PORT) |
--app-port <value> |
Private wrapped application port. (env: TUNNEL_APP_PORT) |
--allow <value> |
Email allow-list patterns. (env: TUNNEL_AUTH_ALLOW) |
--subject <value> |
Verification email subject. (env: TUNNEL_AUTH_SUBJECT) |
--brand-name <value> |
Verification email brand name. (env: TUNNEL_AUTH_BRAND_NAME) |
-m, --message <value> |
Verification email message. (env: TUNNEL_AUTH_MESSAGE) |
--session-ttl-seconds <value> |
Session lifetime in seconds. (env: TUNNEL_AUTH_SESSION_TTL) |
-c, --code-ttl-seconds <value> |
One-time-code lifetime in seconds. (env: TUNNEL_AUTH_CODE_TTL) |
--session-cutoff <value> |
Invalidate sessions issued before this value. (env: TUNNEL_AUTH_SESSION_CUTOFF) |
--storage <value> |
Authentication database mode. (choices: “auto”, “lakebase”, “sqlite”, env: TUNNEL_AUTH_STORAGE) |
--sqlite-path <value> |
Local authentication SQLite file. (env: TUNNEL_AUTH_SQLITE_PATH) |
--forward-headers <value> |
Additional forwarded request header patterns. (env: TUNNEL_FORWARD_HEADERS) |
-g, --gate-paths <value> |
Additional path prefixes requiring authentication. (env: TUNNEL_GATE_PATHS) |
--bind-hosts <value> |
Interface IPs the gate listens on. (env: BIND_HOSTS) |
-i, --insecure |
Run without an authentication gate. (env: TUNNEL_INSECURE) |
--no-insecure |
Disable run without an authentication gate. |
--frp-server <value> |
FRP control host. (env: FRP_SERVER) |
--frp-public-domain <value> |
FRP public HTTP domain. (env: TUNNEL_FRP_PUBLIC_DOMAIN) |
--frp-server-port <value> |
FRP control port. (env: FRP_SERVER_PORT) |
--frp-protocol <value> |
FRP transport protocol. (env: FRP_PROTOCOL) |
--frp-token <value> |
FRP authentication token. (env: FRP_TOKEN) |
--frp-proxy-name <value> |
FRP proxy registration name. (env: FRP_PROXY_NAME) |
dbx tunnel install
Section titled “dbx tunnel install”Install public tunnel client binaries and exit
dbx tunnel install [transport]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
transport |
portr, frp, or both (default: “portr”) |
dbx lakebase-proxy
Section titled “dbx lakebase-proxy”Run a loopback PostgreSQL proxy for Databricks Lakebase
dbx lakebase-proxy [options] [command]Options
Section titled “Options”| Option | Description |
|---|---|
-V, --version |
output the version number |
--postgres-role <value> |
PostgreSQL role assumed after authentication. (env: DBX_TOOLS_POSTGRES_ROLE) |
-l, --listen <value> |
Loopback listener address. (default: tcp://localhost:5432, env: LISTEN) |
-s, --startup-timeout-seconds <value> |
Startup timeout in seconds. (default: 30, env: STARTUP_TIMEOUT_SECONDS) |
--profile <value> |
Exact Databricks profile. (env: DATABRICKS_CONFIG_PROFILE) |
Commands
Section titled “Commands”| Command | Description |
|---|---|
url [options] |
Format a local PostgreSQL URL for a Lakebase target |
service |
Install and manage the desktop service |
dbx lakebase-proxy url
Section titled “dbx lakebase-proxy url”Format a local PostgreSQL URL for a Lakebase target
dbx lakebase-proxy url [options]Options
Section titled “Options”| Option | Description |
|---|---|
-t, --target <value> |
Lakebase project, resource path, host, or URL. (env: TARGET) |
--listen <value> |
Local proxy address. (default: tcp://localhost:5432, env: LISTEN) |
dbx lakebase-proxy service
Section titled “dbx lakebase-proxy service”Install and manage the desktop service
dbx lakebase-proxy service [command]Commands
Section titled “Commands”| Command | Description |
|---|---|
install [options] |
Install the service for the current user and start it |
start |
Start the installed service |
stop |
Stop the running service |
restart |
Restart the installed service |
status |
Print service installation and process state as JSON |
logs [command...] |
Print the service log path or append it to a command |
uninstall |
Stop and remove the service for the current user |
dbx lakebase-proxy service install
Section titled “dbx lakebase-proxy service install”Install the service for the current user and start it
dbx lakebase-proxy service install [options]Options
Section titled “Options”| Option | Description |
|---|---|
--no-start |
Do not start the service after installation |
--python-project <path> |
Install a local Python project instead of the registry package |
--offline |
Install Python packages from the uv cache without network access |
--postgres-role <value> |
PostgreSQL role assumed after authentication. (env: DBX_TOOLS_POSTGRES_ROLE) |
-l, --listen <value> |
Loopback listener address. (default: tcp://localhost:5432, env: LISTEN) |
-s, --startup-timeout-seconds <value> |
Startup timeout in seconds. (default: 30, env: STARTUP_TIMEOUT_SECONDS) |
--profile <value> |
Exact Databricks profile. (env: DATABRICKS_CONFIG_PROFILE) |
dbx lakebase-proxy service start
Section titled “dbx lakebase-proxy service start”Start the installed service
dbx lakebase-proxy service startdbx lakebase-proxy service stop
Section titled “dbx lakebase-proxy service stop”Stop the running service
dbx lakebase-proxy service stopdbx lakebase-proxy service restart
Section titled “dbx lakebase-proxy service restart”Restart the installed service
dbx lakebase-proxy service restartdbx lakebase-proxy service status
Section titled “dbx lakebase-proxy service status”Print service installation and process state as JSON
dbx lakebase-proxy service statusdbx lakebase-proxy service logs
Section titled “dbx lakebase-proxy service logs”Print the service log path or append it to a command
dbx lakebase-proxy service logs [command...]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
command |
Command and arguments to run before the service log path |
dbx lakebase-proxy service uninstall
Section titled “dbx lakebase-proxy service uninstall”Stop and remove the service for the current user
dbx lakebase-proxy service uninstalldbx model-gateway
Section titled “dbx model-gateway”Run or manage the AppKit Databricks model gateway
dbx model-gateway [options] [command]Options
Section titled “Options”| Option | Description |
|---|---|
-v, --version |
output the version number |
--model <value> |
Optional fuzzy or exact model name. (env: MODEL) |
--model-class <value> |
Optional model capability class used when selecting a default model. (choices: “chat-thinking”, “chat-balanced”, “chat-fast”, “embedding”, env: MODEL_CLASS) |
-l, --listen <value> |
Loopback listener address. (default: tcp://localhost:4000, env: LISTEN) |
-p, --profile <value> |
Databricks profile used for model discovery and requests. (env: DATABRICKS_CONFIG_PROFILE) |
--body-limit <value> |
Maximum JSON request body size. (default: “100mb”, env: BODY_LIMIT) |
-r, --runtime-info |
Print runtime implementation metadata. (default: false, env: RUNTIME_INFO) |
--no-runtime-info |
Disable print runtime implementation metadata. |
Commands
Section titled “Commands”| Command | Description |
|---|---|
service |
Install and manage the desktop service |
dbx model-gateway service
Section titled “dbx model-gateway service”Install and manage the desktop service
dbx model-gateway service [command]Commands
Section titled “Commands”| Command | Description |
|---|---|
install [options] |
Install the service for the current user and start it |
start |
Start the installed service |
stop |
Stop the running service |
restart |
Restart the installed service |
status |
Print service installation and process state as JSON |
logs [command...] |
Print the service log path or append it to a command |
uninstall |
Stop and remove the service for the current user |
dbx model-gateway service install
Section titled “dbx model-gateway service install”Install the service for the current user and start it
dbx model-gateway service install [options]Options
Section titled “Options”| Option | Description |
|---|---|
--no-start |
Do not start the service after installation |
--python-project <path> |
Install a local Python project instead of the registry package |
--offline |
Install Python packages from the uv cache without network access |
dbx model-gateway service start
Section titled “dbx model-gateway service start”Start the installed service
dbx model-gateway service startdbx model-gateway service stop
Section titled “dbx model-gateway service stop”Stop the running service
dbx model-gateway service stopdbx model-gateway service restart
Section titled “dbx model-gateway service restart”Restart the installed service
dbx model-gateway service restartdbx model-gateway service status
Section titled “dbx model-gateway service status”Print service installation and process state as JSON
dbx model-gateway service statusdbx model-gateway service logs
Section titled “dbx model-gateway service logs”Print the service log path or append it to a command
dbx model-gateway service logs [command...]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
command |
Command and arguments to run before the service log path |
dbx model-gateway service uninstall
Section titled “dbx model-gateway service uninstall”Stop and remove the service for the current user
dbx model-gateway service uninstalldbx genie
Section titled “dbx genie”Run Genie Code through an authenticated local Databricks model gateway
dbx genie [options] [genieArgs...]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
genieArgs |
arguments and unknown flags forwarded to Genie Code; wrapper options may be separated with – |
Options
Section titled “Options”| Option | Description |
|---|---|
--model <value> |
Optional fuzzy or exact model name. (env: MODEL) |
--model-class <value> |
Optional chat capability class used when selecting a default model. (choices: “chat-thinking”, “chat-balanced”, “chat-fast”, env: MODEL_CLASS) |
-p, --profile <value> |
Databricks profile used by the model-gateway sidecar. (env: DATABRICKS_CONFIG_PROFILE) |
-g, --gateway-listen <value> |
Loopback listener allocated for the model-gateway sidecar. (default: tcp://127.0.0.1:0, env: GATEWAY_LISTEN) |
dbx graphiti
Section titled “dbx graphiti”Run Graphiti or manage its current-user desktop service
dbx graphiti [options] [command]Options
Section titled “Options”| Option | Description |
|---|---|
-v, --version |
output the version number |
--profile <value> |
Databricks profile used for model discovery and authentication. (env: DATABRICKS_CONFIG_PROFILE) |
-b, --bearer <value> |
Optional bearer token required by every Graphiti HTTP endpoint. (env: GRAPHITI_TOKEN) |
-g, --graphiti-home <value> |
Application-owned Graphiti runtime directory. (env: GRAPHITI_HOME) |
-m, --model-class <value> |
Optional chat capability class used when selecting a default model. (choices: “chat-thinking”, “chat-balanced”, “chat-fast”, default: “chat-fast”, env: MODEL_CLASS) |
-t, --temperature <value> |
Sampling temperature forwarded to the Graphiti LLM client. (default: 1, env: TEMPERATURE) |
--structured-output-mode <value> |
Structured-output mode forwarded to Graphiti’s OpenAI provider. (default: “json_object”, env: LLM_STRUCTURED_OUTPUT_MODE) |
--startup-timeout-ms <value> |
Maximum milliseconds allowed for the Graphiti runtime to become ready. (default: 180000, env: DBX_TOOLS_GRAPHITI_STARTUP_TIMEOUT_MS) |
-l, --listen <value> |
Graphiti HTTP listener. (default: tcp://127.0.0.1:7272, env: GRAPHITI_LISTEN) |
--database-url <value> |
PostgreSQL URL or Lakebase target. Omit it to use persistent embedded PostgreSQL. (env: LAKEBASE_ENDPOINT) |
--database-schema <value> |
PostgreSQL schema used for Lakebase graph tables. (default: “dbx_tools_graphiti”, env: GRAPHITI_DATABASE_SCHEMA) |
--postgres-role <value> |
PostgreSQL role assumed after authentication. (env: DBX_TOOLS_POSTGRES_ROLE) |
Commands
Section titled “Commands”| Command | Description |
|---|---|
service |
Install and manage the desktop service |
dbx graphiti service
Section titled “dbx graphiti service”Install and manage the desktop service
dbx graphiti service [command]Commands
Section titled “Commands”| Command | Description |
|---|---|
install [options] |
Install the service for the current user and start it |
start |
Start the installed service |
stop |
Stop the running service |
restart |
Restart the installed service |
status |
Print service installation and process state as JSON |
logs [command...] |
Print the service log path or append it to a command |
uninstall |
Stop and remove the service for the current user |
dbx graphiti service install
Section titled “dbx graphiti service install”Install the service for the current user and start it
dbx graphiti service install [options]Options
Section titled “Options”| Option | Description |
|---|---|
--no-start |
Do not start the service after installation |
--python-project <path> |
Install a local Python project instead of the registry package |
--offline |
Install Python packages from the uv cache without network access |
dbx graphiti service start
Section titled “dbx graphiti service start”Start the installed service
dbx graphiti service startdbx graphiti service stop
Section titled “dbx graphiti service stop”Stop the running service
dbx graphiti service stopdbx graphiti service restart
Section titled “dbx graphiti service restart”Restart the installed service
dbx graphiti service restartdbx graphiti service status
Section titled “dbx graphiti service status”Print service installation and process state as JSON
dbx graphiti service statusdbx graphiti service logs
Section titled “dbx graphiti service logs”Print the service log path or append it to a command
dbx graphiti service logs [command...]Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
command |
Command and arguments to run before the service log path |
dbx graphiti service uninstall
Section titled “dbx graphiti service uninstall”Stop and remove the service for the current user
dbx graphiti service uninstall