# Prepare the CLI in the environment your agent uses

Illustrative planning brief; no automatic product import.

Illustrative case: a Windows CLI exists, but an agent runs in WSL and cannot resolve teamboost on its own PATH.

## Decision

Use the supported executable for the agent’s runtime and verify its command interface there.

## Owned work

- Identify the runtime
  - Owner role: Operator
  - Acceptance evidence: OS/CPU and the terminal used by the agent are confirmed.
- Verify the supported artifact
  - Owner role: Operator
  - Acceptance evidence: The distribution checksum and runtime prerequisites are checked before installation.
- Check local discovery
  - Owner role: Agent user
  - Acceptance evidence: Version/help resolve in that runtime; the full skill folder is discoverable separately.

## Workflow

1. Identify Windows, WSL or another actual execution environment.
2. Use TeamBoost’s supported distribution and checksum.
3. Check version/help, then authenticate through the normal browser flow when ready.

## Judgment

Do not install a similarly named registry package. These pages do not supply or run an installer.


## Illustrative installation checklist

Agent runtime: confirm before choosing the archive.
Executable: supported TeamBoost distribution with matching checksum.
Skill: full folder including references, installed for that agent.
Session: normal browser-authenticated login, not copied credentials.


## Workflow questions

### Does installing the skill install the executable?

No. The source skill contains guidance, not the native binary or a user session.

### Do Windows and WSL share PATH automatically?

Treat them as distinct runtimes and verify the command where the agent actually executes it.

## Product connection

Prepare the executable, agent instructions and account context separately before using the source-backed TeamBoost CLI workflow.

Confirm account availability before adopting this manual outline.