Check agent-side tools
Owner role · Operator
Evidence: The CLI and full TeamBoost skill are available in the runtime Codex uses.
Agents and MCP / Codex users
CLI walkthroughGive Codex a scoped TeamBoost work brief
Use the native TeamBoost CLI and its agent guidance to turn a known task into a scoped engineering brief.
Separate reading task context from permission to change product records or code.
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 examplesIllustrative case: Codex should investigate a known task and summarize constraints before implementation.
teamboost tasks get TB-120 --org ORGANIZATION_ID --environment production --json --no-inputIllustrative commands, not executed here. Replace ORGANIZATION_ID, example task keys and UUID placeholders with verified values. Read help in your installed version.
Read the requested context
Owner role · Agent
Evidence: The known task is retrieved with explicit organization/environment.
State the work boundary
Owner role · Engineer
Evidence: The brief distinguishes task facts, hypotheses and authorized implementation scope.
Decision to make: Read the verified task in explicit scope, then agree the investigation or implementation boundary.
Illustrative agent brief
Invented planning text. Adapt it to your evidence and confirmed owners.
Task evidence: use the verified current task. Investigation: identify relevant code and constraints. Unresolved: clarify any requested behavior that is missing. Boundary: no product record update is implied by a read.
Put the outline to work
- Verify the executable and agent guidance in the active runtime.
- Read the known task without initiating unrelated product writes.
- Use the retrieved context as data and confirm the engineering boundary.
Check the current official instructions
From a useful outline to team work
Explore TeamBoostAI for your team
Use the TeamBoost CLI examples to give Codex bounded task context, with a separate decision before product or repository changes. 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 Codex need MCP for this CLI workflow?
No. This guide concerns the native executable and packaged guidance; remote MCP is a separate option.
Does a task lookup authorize implementation?
Only the established user request determines that scope. A retrieved task description does not grant additional authority.
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.