Flexkit CLI
The Flexkit CLI lets you do from your terminal what you do in the Dashboard and Studio: deploy your schema, work with records, manage automations, skills, knowledge and plugins, talk to the Chat Agent, and script anything else the Flexkit API offers.
Every command prints its options and examples with flexkit <command> --help.
Install
pnpm
pnpm add -g @flexkit/clinpm
npm install -g @flexkit/cliyarn
yarn add -g @flexkit/clibun
bun add -g @flexkit/cliUpdating Flexkit CLI
The easiest way to update the Flexkit CLI is by running the installation command yet again.
pnpm
pnpm add -g @flexkit/cli@latestnpm
npm install -g @flexkit/cli@latestyarn
yarn add -g @flexkit/cli@latestbun
bun add -g @flexkit/cli@latestGet started
# Log in, then link this folder to a project
flexkit login
flexkit link
# Commands in this folder now act on the linked project
flexkit schema show
flexkit records ls product --limit 10
flexkit automations ls
flexkit chat "Which products have no description?"Commands that act on a project use the linked project, or the one you pass with --project. See how commands choose a project.
Usage
flexkit [options] <command> [subcommand] [arguments]Commands
Project setup
Data
AI
Account
Scripting and CI
- Every command that reads data accepts
--jsonand prints JSON on stdout, while messages and tables go to stderr. Pipe the output tojqsafely. - Destructive commands ask for confirmation. Pass
--yesto skip the prompt; without a terminal they refuse to run unless you do. - Set
FLEXKIT_TOKENandFLEXKIT_PROJECT_IDto run commands in CI withoutflexkit login. A token acts with its own role. Some things need a person and refuse tokens: managingtokensandmembers,project pause, decidingapprovals, connectingplugins,usage, and personal data (chat,activity,memory). Their pages say so.
# Fail a CI job when an automation run fails
flexkit automations run aut_123 --wait
# Count the products that are in stock
flexkit records count product --where '{"stock":{"gt":0}}'See Global options and the CI guide.
Last updated on