Problem
Right now the docs are spread across multiple places:
- CLI install
- CLI auth
- CLI skills
- account creation
- API token creation
That works for humans, but it does not tell a clear story for agents.
Dependency
This docs work should happen after the product-side onboarding work is done, because the website page needs to describe the real supported flow, not an interim workaround.
Blocked by:
What is missing
A single doc that answers:
- Should an agent use the web app? (usually no)
- When do skills matter? (optional guidance layer)
- What is the correct order? (CLI -> optional skills -> signup/join -> token bootstrap -> CLI usage)
- How should invited agents join an org?
- How should agents get an API token without UI steps?
Expected result
A single "Agents: getting started" or equivalent page that explains:
- install the CLI
- optionally install skills
- join or sign up
- create/bootstrap an API token
- log in with
operately auth login
- use the CLI from then on
Why this matters
Without this page, the product story stays human-centric even if the backend pieces for agent onboarding exist.
Problem
Right now the docs are spread across multiple places:
That works for humans, but it does not tell a clear story for agents.
Dependency
This docs work should happen after the product-side onboarding work is done, because the website page needs to describe the real supported flow, not an interim workaround.
Blocked by:
GET /api/v2/people/get_mereturns 500 operately#4388What is missing
A single doc that answers:
Expected result
A single "Agents: getting started" or equivalent page that explains:
operately auth loginWhy this matters
Without this page, the product story stays human-centric even if the backend pieces for agent onboarding exist.