stackkit setup

Set up the owner account of an applied application. Run a Plan-declared setup action on the existing local application. Read the private credential JSON fields and file path from the selected application’s setup guide or status action. Credentials are never written into lifecycle evidence. Re-running after interruption re-observes the application before completing the same pending setup operation.

stackkit setup <workload> [flags]

Flag	Type	Default	Description
`--complete-onboarding`	bool	—	Complete the app user and administrator onboarding after verifying the owner login
`--credentials-file`	string	—	Workspace-relative private owner credential JSON file (defaults to the selected application’s setup guide)
`--json`	bool	—	Emit the secret-free verified setup result
`--media-file`	string	—	Import one owner-supplied file from media-import/ into the applied Jellyfin named library, then scan it
`--operation-id`	string	—	Resume a pending setup operation; defaults to the current pending setup or a new ID
`--owner-approve`	bool	—	Approve this Plan-bound application setup

Examples

# Create the Photos owner from the private credentials in .stackkit/setup/owner.json
stackkit setup photos --owner-approve

# Also finish the application's onboarding after the owner login is verified
stackkit setup photos --owner-approve --complete-onboarding

# Create the Files owner from a workspace-relative credentials file of your choice
stackkit setup files --owner-approve --credentials-file private/files-owner.json

Subcommands: stackkit setup ai-connect, stackkit setup ai-provider, stackkit setup connector

stackkit setup ai-connect

Connect the Private AI Ollama to your kombify AI as an own model endpoint. Turn on the optional kombify AI connector of the Private AI use case. Create a model endpoint in Companion Studio (Settings, AI access, Model endpoints) with the origin http://ollama:11434 and copy its connector token. This command reads the token from standard input or from --token-file, never from an argument, checks its shape, keeps it in local owner custody and turns the connector on. The next generate and apply start the outbound connector next to Ollama. Nothing inbound is opened and Ollama stays unpublished. --disable turns the connector off and removes the token from local custody. Revoke the endpoint in Companion Studio to make the token useless everywhere.

stackkit setup ai-connect [flags]

Flag	Type	Default	Description
`--disable`	bool	—	Turn the connector off and remove its token from local custody
`--json`	bool	—	Emit the secret-free result
`--token-file`	string	—	File with the connector token; ”-” or no flag reads standard input

Examples

# Paste the connector token, then press Enter and Ctrl-D (or read it hidden on a terminal)
stackkit setup ai-connect --token-file -

# Read the token from a private file
stackkit setup ai-connect --token-file ~/kombify-connector-token

# Turn the connector off and remove its token
stackkit setup ai-connect --disable

stackkit setup ai-provider

Offer an external OpenAI-compatible provider in Private AI with a key from your kombify Wallet. Let Open WebUI of the Private AI use case use an external OpenAI-compatible inference provider (for example OpenAI, Mistral, Groq or OpenRouter) next to the node’s Ollama. The provider’s API key never passes through this command, the StackSpec or the generated bundle: keep it as an AI credential in your kombify Wallet, allow this node on the item, and deliver it sealed to this node with “stackkit wallet-item import”. This command binds the provider key to that delivered item and sets the provider’s https base URL. Every apply then reads the newest delivered version, so a rotation in the Wallet takes effect after “stackkit wallet-item import” of the rotated item and the next apply. Apply fails closed when the item is not in this node’s custody. --disable removes the provider from Open WebUI and the binding from local custody. The delivered item stays in the node’s Wallet item custody.

stackkit setup ai-provider [flags]

Flag	Type	Default	Description
`--base-url`	string	—	https base URL of the OpenAI-compatible provider API
`--disable`	bool	—	Remove the external provider and its key binding
`--json`	bool	—	Emit the secret-free stackkit.command-result/v1 result
`--tenant-ref`	string	—	Tenant the Wallet item was delivered under
`--wallet-item`	string	—	Wallet item reference of the delivered provider key

Examples

# Bind the provider key delivered as Wallet item itm_... and set the provider
stackkit setup ai-provider --base-url https://api.openai.com/v1 --tenant-ref "$TENANT" --wallet-item itm_abc...

# Remove the provider
stackkit setup ai-provider --disable

stackkit setup connector

Issue, revoke or verify the exact local Home Assistant connector.

stackkit setup connector [flags]

Flag	Type	Default	Description
`--json`	bool	—	Emit the authenticated exact signed receipt bytes and current local facts
`--operation-id`	string	—	Exact stable connector setup operation identity
`--owner-approve`	bool	—	Approve this exact connector ensure or revoke request
`--request-file`	string	—	Workspace-relative private metadata-only connector request JSON; never contains credentials
`--verify-only`	bool	—	Read and verify a retained receipt against current local binding without issuing or revoking
`--workload`	string	—	Exact local workload; only smart-home is admitted

Get started

Get help

Guides

Reference

stackkit setup ai-connect

stackkit setup ai-provider

stackkit setup connector

​stackkit setup ai-connect

​stackkit setup ai-provider

​stackkit setup connector

stackkit setup ai-connect

stackkit setup ai-provider

stackkit setup connector