TeamBoostWORKFLOW LIBRARY

Command-line workflows / CLI users

CLI walkthrough

Check your TeamBoost CLI workspace before work

Establish account, environment and organization readiness before reading or proposing a task change.

Keep a healthy login separate from a selected and accessible organization.

Request TeamBoostAI accessGet the work briefTask table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Work through the command boundary

Source-backed CLI examples

Illustrative case: a new terminal has a valid session but no organization default. The next task request must not silently choose a workspace.

teamboost / example commands
teamboost org current --json --no-input

teamboost org list --all --json --no-input

teamboost doctor --org ORGANIZATION_ID --environment production --json --no-input

Illustrative commands, not executed here. Replace ORGANIZATION_ID, example task keys and UUID placeholders with verified values. Read help in your installed version.

01

Inspect current context

Owner role · CLI user

Evidence: Record whether an organization is selected, without exposing account values.

02

Discover accessible memberships

Owner role · CLI user

Evidence: Find the intended workspace in the membership results and resolve ambiguous names.

03

Check readiness in scope

Owner role · Workflow owner

Evidence: Doctor results distinguish authentication, organization access and version health.

Decision to make: Resolve the intended organization from accessible memberships, then carry its scope into later commands.

Illustrative readiness decision

Invented planning text. Adapt it to your evidence and confirmed owners.

Session: check separately from workspace selection.
Workspace: choose the user-requested membership, not the first returned item.
Next action: use that verified organization explicitly; investigate any failing check.

Put the outline to work

  1. Inspect current context without changing it.
  2. Resolve the intended workspace before selecting a persistent default.
  3. Use explicit scope in subsequent commands and stop on access errors.

Continue with a related decision

Command-line workflowsPrepare the CLI in the environment your agent usesAgents and MCPCheck the workspace boundary of an MCP connection

From a useful outline to team work

Explore TeamBoostAI for your team

The source-backed TeamBoost CLI distinguishes authentication from workspace readiness; verify the installed version and account scope before using these examples. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Questions about this workflow

Does doctor choose an organization?

No. Inspect its organization result; readiness and a saved default are separate conditions.

Should I log out after an API error?

Inspect the error first. A scope or route failure does not establish that the session is invalid.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.