Projects

​

Why Projects?

• Isolate environments — keep production resources apart from staging or experiments.
• Scope access — issue API keys that can only see resources in one project.
• Per-project limits — cap concurrency on a per-project basis so one team or environment can’t exhaust your org quota.

​

The Default Project

{ "code": "conflict", "message": "organization must have at least one project" }

​

Scoping Requests to a Project

curl https://api.onkernel.com/browsers \
  -H "Authorization: Bearer $KERNEL_API_KEY" \
  -H "X-Kernel-Project-Id: proj_abc123"

​

SDK usage

import Kernel from '@onkernel/sdk';

// Scope the whole client to a project
const kernel = new Kernel({
  defaultHeaders: { 'X-Kernel-Project-Id': 'proj_abc123' },
});

const browser = await kernel.browsers.create();

// Or override per-request
const other = await kernel.browsers.create(
  {},
  { headers: { 'X-Kernel-Project-Id': 'proj_def456' } },
);

from kernel import Kernel

# Scope the whole client to a project
kernel = Kernel(
    default_headers={"X-Kernel-Project-Id": "proj_abc123"},
)

browser = kernel.browsers.create()

# Or override per-request
other = kernel.browsers.create(
    extra_headers={"X-Kernel-Project-Id": "proj_def456"},
)

​

Authentication and Project Scope

​

API keys

• Existing API keys are org-wide. They see every resource in your organization across all projects. Include an X-Kernel-Project-Id header to restrict a single request to one project.
• Project-scoped API keys can only access resources inside the project they were issued for. Create one from the API Keys page in the dashboard and pick the target project when generating the key. Requests made with a scoped key are automatically limited to that project — no header required. If you do send an X-Kernel-Project-Id header and it conflicts with the key’s project, the request is rejected with 403 Forbidden.

​

OAuth

​

Using Projects from the CLI

• A global --project <id-or-name> flag scopes any command to a single project. Names are resolved case-insensitively, so --project staging works.
• The KERNEL_PROJECT environment variable does the same, so you can set it once in your shell or CI.
• A kernel projects command group lets you list, create, get, and delete projects, and manage per-project limit overrides.

# Scope a single command
kernel browsers list --project staging

# Scope every command in the shell
export KERNEL_PROJECT=staging
kernel apps list

# Manage projects
kernel projects list
kernel projects create staging
kernel projects limits set staging --max-concurrent-sessions 5

​

Managing Projects

​

Create a project

import Kernel from '@onkernel/sdk';

const kernel = new Kernel();

const project = await kernel.projects.create({ name: 'staging' });
console.log(project.id); // proj_abc123

from kernel import Kernel

kernel = Kernel()

project = kernel.projects.create(name="staging")
print(project.id)  # proj_abc123

​

List projects

for await (const project of kernel.projects.list()) {
  console.log(project.id, project.name, project.status);
}

for project in kernel.projects.list():
    print(project.id, project.name, project.status)

​

Update a project

await kernel.projects.update('proj_abc123', { name: 'production' });

kernel.projects.update("proj_abc123", name="production")

​

Delete a project

await kernel.projects.delete('proj_abc123');

kernel.projects.delete("proj_abc123")