Managing your organisation
Organisations and projects
How workspaces, repositories, and URLs map in ctx|.
ctx| is multi-tenant. Almost everything you care about — repositories, conversations, API keys scoped to an org context — lives under an organisation.
Organisations
- On first sign-in, ctx| creates a personal organisation for you and sets it active on your session (Better Auth organisation plugin + backend hooks).
- Each org has a human-readable name, a URL-safe slug (globally unique),
and an internal ID (
org_<base32>style in the API). - The browser app routes as
/:orgSlug/.... Switching org updates that slug.
“Projects” in practice
The product surface centres on repositories under an org — think of each registered repo (or monorepo) as the unit of code connection and ingestion. There is no separate “project” entity name in the public API docs; grouping is by organisation + repository list.
Org context for APIs and MCP
- REST (versioned, org-scoped):
/:orgSlug/api/v1/...for repositories, conversations, GitHub installation setup, etc. - MCP:
GET/POST /mcp?orgSlug=<slug>— the slug is required; the backend resolves it to an org ID and checks membership.
Creating additional organisations
You can create orgs via the Better Auth organisation APIs (or product UI where exposed). The authenticated user becomes owner of the new org.