Each path below starts from a different situation. Pick the one that matches how you are arriving.
Try Spor locally
Use this when you want to see Spor work before involving a team or a server; local mode keeps Spor’s record as plain markdown files in a git repository on your machine, with no server and no account. You install the CLI, record your first item of work, and read the ranked queue of open work. Try Spor locally.
I was invited to hosted Spor
Use this when your team already runs Spor and you have an invite. Join with an invite token (spor join) or interactive sign-in (spor auth login), then make your first capture and read the team’s shared queue; writes are attributed to you. I was invited to hosted Spor.
Connect an assistant
Use this when you want claude.ai or Claude Code to read and write your team’s Spor records. Give the assistant one connector URL and approve access in the browser sign-in flow; anything it records is attributed to you. Connect an assistant.
Build an integration
Use this when you are building your own tooling against Spor. The CLI and connectors use the same plain HTTPS and JSON API, versioned under /v1/ and authenticated with a bearer token. REST API reference.
If you want the mental model before choosing, start with Core ideas.