Projects.

The routes that start and follow a Deploy are on Deploys. Setup commands, services and environment variables are on Project settings.

A chat session's sandbox token and a Cron Run's token reach the live routes only in their own project: the session's project, or a project the Cron Run covers. Another project of the same workspace answers 403.

List projects

List every project in every workspace you belong to, newest first.

curl -s https://app.kosuke.ai/api/projects \
  -H "Authorization: Bearer $KOSUKE_API_KEY"

{
  "data": [
    {
      "id": "3f6c1e0a-8b2d-4e57-9a41-0c2f7d9b5e18",
      "name": "storefront",
      "description": null,
      "orgId": "YzH4k2P9sQ1mVx7bN3cR8tL5wD0fG6jA",
      "githubRepoUrl": "https://github.com/acme/storefront",
      "githubOwner": "acme",
      "githubRepoName": "storefront",
      "defaultBranch": "main",
      "deploymentStatus": "deployed",
      "sandboxTier": "MEDIUM",
      "createdAt": "2026-08-14T09:20:11.000Z",
      "sessions": [
        {
          "id": "b1d6e2f4-7a3c-4c1e-9f0b-2e8d5a6c7b90",
          "title": "Fix the checkout total",
          "branchName": "kosuke/chat-x7k2m9",
          "messageCount": 6,
          "status": "active",
          "lastActivityAt": "2026-09-30T09:02:44.000Z"
        }
      ]
    }
  ]
}

orgId is the workspace the project belongs to. sessions holds the project's active, under-review and completed sessions that have a branch, most recently active first. For every session, use Chat sessions.

GET /api/projects/{projectId} reads one project. It has the same fields without sessions, and adds credentialOwners, whose credentials the project's own sandbox runs each provider on.

In the CLI, run kosuke projects list and kosuke projects get <projectId>.

Create a project

Import a repository into a workspace. Any member of the workspace can.

1. Find the workspace id with GET /api/organizations. See Workspaces.
2. Pick the repository from GET /api/auth/github/repositories, one whose appInstalled is true. See GitHub to install the Kosuke App on another one.
3. Send the request below.

curl -s https://app.kosuke.ai/api/projects \
  -H "Authorization: Bearer $KOSUKE_API_KEY" \
  --json '{
    "name": "storefront",
    "repositoryUrl": "https://github.com/acme/storefront",
    "orgId": "YzH4k2P9sQ1mVx7bN3cR8tL5wD0fG6jA"
  }'

The route answers 201 with the new project in data.project.

Importing also brings the repository's open pull requests in as chat sessions. A draft pull request becomes an active session, and one ready for review an under-review session. These sessions have no Assignee.

Creating the project starts its first Deploy, as you, the same as an import in the web app. Follow it with Deploys. When the workspace has no deploy model it can run, the Deploy does not start, and the Deploy Chat says why. Sessions start once the first Deploy lands. Backlog sessions can be filed at once.

In the CLI, run kosuke projects create --name storefront --repository-url https://github.com/acme/storefront --org-id <workspaceId>.

To create the project in your Personal instead, send "personal": true in place of orgId, or pass --personal in the CLI. It needs your own credential, or your Sensei in a Turn your own message started. A chat session's sandbox token, a Cron Run's token and Sensei in any other Turn answer 403. A Personal import checks your own GitHub Connection, even for a Superadmin.

Rename a project

Any member can rename a project. The route answers 200 with the updated project.

curl -s -X PATCH https://app.kosuke.ai/api/projects/$PROJECT_ID \
  -H "Authorization: Bearer $KOSUKE_API_KEY" \
  --json '{ "name": "storefront-web" }'

In the CLI, run kosuke projects update <projectId> --name storefront-web.

Delete a project

Workspace owners and admins can delete a project. The route answers 204.

curl -s -X DELETE https://app.kosuke.ai/api/projects/$PROJECT_ID \
  -H "Authorization: Bearer $KOSUKE_API_KEY"

The repository on GitHub stays as it is, with its branches and pull requests. The workspace's usage records and Activity keep the project's past entries.

In the CLI, run kosuke projects delete <projectId>.

Branches

List the repository's branches, 30 per page in alphabetical order.

curl -s "https://app.kosuke.ai/api/projects/$PROJECT_ID/branches?search=release" \
  -H "Authorization: Bearer $KOSUKE_API_KEY"

{
  "data": {
    "branches": ["release/2026-09", "release/2026-10"],
    "defaultBranch": "main",
    "nextCursor": null
  }
}

defaultBranch is the branch new sessions start from. It is the project's own setting when one is saved, otherwise the repository's default branch. nextCursor is null on the last page.

In the CLI, run kosuke projects branches list <projectId> --search release.

Skills available in a project

List the skills and commands a session in this project can run. In a session, the composer menu also shows the Runtime Commands /clear and /compact ($clear and $compact in Codex sessions), which this route does not return. provider is required. Pass anthropic for Claude, GLM, Kimi and DeepSeek sessions, openai for Codex sessions, meta for Muse Code sessions, google for Gemini sessions, or xai for Grok sessions. Add sessionId to read the repository's skills from that session's sandbox while it is running, and to list the Personal Skills of that session's Assignee; otherwise the list comes from the project's main sandbox or the last cached list.

curl -s "https://app.kosuke.ai/api/projects/$PROJECT_ID/skills?provider=anthropic" \
  -H "Authorization: Bearer $KOSUKE_API_KEY"

{
  "data": {
    "skills": [
      {
        "slug": "kosuke:sync-branch",
        "name": "sync-branch",
        "description": "Bring the current branch up to date with the branch its pull request targets: …",
        "argumentHint": "[--target-branch <branch>]",
        "kind": "skill",
        "origin": "kosuke",
        "source": "kosuke"
      }
    ]
  }
}

To run a skill in a session, send its invocation as a message. See Messages and turns.

In the CLI, run kosuke projects skills list <projectId> --provider anthropic.

Chat

A repository's Chat is one session per project that works on the default branch and pushes there itself, with no pull request. Read it for yourself with GET: the answer depends on who asks, because the push is made with your GitHub account, or by Kosuke on a repository Kosuke made.

curl -s "https://app.kosuke.ai/api/projects/$PROJECT_ID/chat" \
  -H "Authorization: Bearer $KOSUKE_API_KEY"

{
  "data": {
    "availability": { "on": true, "branch": "main", "pusher": "member" },
    "session": { "id": "2b0c6f2e-5a51-4c55-9a8e-0f3c1d9e7a10", "status": "active" },
    "pushes": [
      {
        "chatJobId": "8d7e1f4a-3c2b-4d6e-9f10-2a3b4c5d6e7f",
        "commitSha": "4f9c2a1e7b3d5c6a8e0f1b2c3d4e5f6a7b8c9d0e",
        "versionNumber": 12,
        "pushedAt": "2026-11-03T10:24:05.000Z"
      }
    ]
  }
}

Chat is off on an imported repository when you have no GitHub connection, it needs a reconnect, or your account cannot push. On any repository, it is off when a branch protection rule or an active ruleset on the default branch requires pull requests, status checks, signed commits, deployments or a merge queue, blocks updates, or keeps direct pushes out, even when the pusher could bypass it. Use a task instead, and the Merge agent lands it.

Open it with POST, which takes no body. It creates the session the first time and answers the same one after that, so you can send it again safely. No Turn starts: send the first message to session.id as in Messages and turns. Each Turn runs as the member who sent it. A message you send while another member's Turn runs waits in the Queue.

curl -s -X POST "https://app.kosuke.ai/api/projects/$PROJECT_ID/chat" \
  -H "Authorization: Bearer $KOSUKE_API_KEY"

{
  "data": {
    "session": { "id": "2b0c6f2e-5a51-4c55-9a8e-0f3c1d9e7a10", "status": "active" }
  }
}

In the CLI, run kosuke projects chat get <projectId> and kosuke projects chat create <projectId>. See Project settings for the Chat tab in the app.

Errors

The full list is in Responses and errors.

Next steps

• Follow the project's first Deploy with Deploys.
• Configure what runs in its sandbox with Project settings.
• Open a session in it with Chat sessions.