Skip to main content

​
crewship config

Manage CLI configuration stored in ~/.crewship/cli-config.yaml. 
crewship config <subcommand>

​
Subcommands

CommandDescription
showDisplay current configuration
setSet a configuration value
validateSanity-check the saved config (token authenticates, workspace exists, server reachable)

​
crewship config show

Display current CLI configuration including config file path, server, workspace, format, and token status. 
crewship config show

​
crewship config set

Set a configuration value. 
crewship config set <key> <value>
Available keys:
KeyDescription
serverServer URL (e.g., http://localhost:8080).
workspaceDefault workspace slug or ID.
formatDefault output format: table, json, yaml, or quiet.
default-agent (alias: default_agent)Default agent slug used by chat-style commands when --agent is omitted.
markdownMarkdown-rendering toggle for terminal output: on, off, or auto (auto follows TTY detection).
crewship config set server http://localhost:8080
crewship config set workspace my-workspace
crewship config set format json
crewship config set default-agent viktor
crewship config set markdown auto

​
crewship config validate

Sanity-check the saved CLI configuration end-to-end: parse the YAML, dial the server, verify the token authenticates, and confirm the recorded workspace exists for the caller. Useful as a one-shot health check before scripting against the CLI or wiring it into CI. 
crewship config validate

​
Multiple servers

To target several instances (dev/staging/prod) from one config, use server profiles instead of swapping server/token by hand. Each profile carries its own token and is selectable per-command (--profile), per-shell (CREWSHIP_PROFILE), or per-directory. config show prints the active profile when any are defined.

​
See also

  • crewship server — manage named server profiles for multi-instance targeting.
  • crewship workspace — switch / list / create workspaces, manage members and invitations (moved out of this page since config and workspace are distinct surfaces).
  • crewship login — populate server and token interactively.
  • Authentication — how the CLI token is minted and validated end-to-end.