# Check your TeamBoost CLI workspace before work

Illustrative planning brief; no automatic product import.

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

## Decision

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

## Owned work

- Inspect current context
  - Owner role: CLI user
  - Acceptance evidence: Record whether an organization is selected, without exposing account values.
- Discover accessible memberships
  - Owner role: CLI user
  - Acceptance evidence: Find the intended workspace in the membership results and resolve ambiguous names.
- Check readiness in scope
  - Owner role: Workflow owner
  - Acceptance evidence: Doctor results distinguish authentication, organization access and version health.

## Workflow

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.

## Judgment

Doctor readiness is not proof that every API or feature works. These examples do not authenticate or select a workspace for you.


## Illustrative readiness decision

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.


## Illustrative commands (not executed)

```text
teamboost org current --json --no-input
teamboost org list --all --json --no-input
teamboost doctor --org ORGANIZATION_ID --environment production --json --no-input
```


## Workflow questions

### 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.

## Product connection

The source-backed TeamBoost CLI distinguishes authentication from workspace readiness; verify the installed version and account scope before using these examples.

Confirm account availability before adopting this manual outline.