Project

rensei project manages everything scoped to a single Rensei project from the CLI: members and roles, connected repositories, issue-tracker integrations (including the Linear OAuth wizard), runtime tokens, and sandbox access controls.

Members

`project members list`

rensei project members list [--project <slug>] [--json]

rensei project members list
rensei project members list --project my-fintech-app

Example output:

EMAIL                  ROLE     JOINED
mark@acme.com          admin    2024-11-01
sara@acme.com          member   2025-01-14
agent-ci@acme.com      viewer   2025-03-02

`project members add`

Add a member to the project. The user must already be an org member (see rensei org invites create to invite new org members first).

rensei project members add <email> --role member|admin|viewer

rensei project members add sara@acme.com --role admin

`project members update`

Change a project member's role.

rensei project members update <email> --role <role>

rensei project members update sara@acme.com --role viewer

`project members remove`

Remove a member from the project. Does not affect their org membership.

rensei project members remove <email> [--yes]

rensei project members remove former-contractor@acme.com --yes

Repositories

Repositories connected to a project are cloned into agent workareas before each session. Multiple repos can be connected; agents receive all of them.

`project repo list`

rensei project repo list [--project <slug>] [--json]

`project repo add`

Connect a repository to the project.

rensei project repo add <url>

rensei project repo add https://github.com/acme/backend-api
rensei project repo add https://github.com/acme/frontend

The platform detects the VCS provider (GitHub, GitLab, Bitbucket) from the URL and uses the OAuth credential configured for that provider. Ensure the integration is connected first (rensei project trackers add or via the web UI).

`project repo update`

Change the clone strategy for a connected repository.

rensei project repo update <url> [--clone-strategy shallow|full|reference-clone]

Strategy	Description
`shallow`	Depth-1 clone. Fastest, minimal disk. Default for most projects.
`full`	Full history clone. Needed for `git log`-heavy tasks or blame-based tools.
`reference-clone`	Clone from a local reference pack if available; reduces bandwidth on shared hosts.

rensei project repo update https://github.com/acme/backend-api --clone-strategy full

`project repo remove`

Disconnect a repository. Does not delete any existing workareas.

rensei project repo remove <url> [--yes]

Issue trackers

Issue trackers connect the project to Linear, Jira, GitHub Issues, Asana, or other supported systems. Agents use the tracker to read work items, post comments, and update issue status.

`project trackers list`

rensei project trackers list [--project <slug>]

`project trackers add`

Bind an issue tracker by its path ID (e.g. the Linear team key or Jira project key) to a project.

rensei project trackers add <pathId> [<project-slug>] --provider <provider> [--display-name <name>]

Argument	Description
`<pathId>`	Provider-specific identifier, e.g. the Linear team key (`ENG`) or Jira project key (`ACME`)
`<project-slug>`	Project slug (optional; defaults to the active project)

Flag	Description
`--provider`	(Required) Tracker provider: `linear`, `jira`, etc.
`--display-name`	Friendly name shown in listings
`--project`	Target project slug (alternative to positional slug argument)

rensei project trackers add ENG --provider linear
rensei project trackers add ACME --provider jira --display-name "Acme Jira"

To connect Linear with full OAuth (recommended for AgentSession activity), use project trackers connect linear instead. See below.

`project trackers connect linear`

Run the guided Linear OAuth flow. This is the recommended way to connect Linear; it provisions full app:assignable + app:mentionable scopes required for AgentSession activity.

rensei project trackers connect linear \
  [--team <linear-team-uuid>] \
  [--path-id <TEAM>] \
  [--project <slug>] \
  [--no-bind] \
  [--display-name <name>] \
  [--timeout <seconds>]

Flag	Description
`--team`	Linear team UUID to subscribe webhook for (or `RENSEI_LINEAR_TEAM_ID`). Omit to subscribe to all public teams (not recommended for first-time setup).
`--path-id`	Linear team path identifier (e.g. `ENG`). Required when binding the tracker.
`--project`	Project slug to bind the tracker to (defaults to active project).
`--no-bind`	Skip the project-tracker binding step; only establishes the org-level OAuth.
`--display-name`	Friendly name for the tracker binding.
`--timeout`	Maximum time in seconds to wait for OAuth completion (default: 300).

The CLI opens a browser to the Linear OAuth consent screen (or prints the URL if --no-interactive is set).

After you approve, Linear redirects back with an auth code. The CLI exchanges it for an OAuth token.

The token is stored in the platform credential store for this project. Agents running under this project use the platform proxy - they never receive the OAuth token directly.

Using project trackers add with a plain path ID (non-OAuth) provisions user-scope credentials (read,write,issues:create,comments:create) that do not include app:assignable or app:mentionable. AgentSession activity (agent thoughts, responses visible in the Linear UI) requires the OAuth flow via connect linear. See Linear integration for details.

`project trackers update`

Update tracker configuration (e.g., rotate a credential).

rensei project trackers update <tracker-id>

`project trackers remove`

Disconnect a tracker.

rensei project trackers remove <tracker-id> [--yes]

Runtime tokens

Project tokens (rsp_live_*) are used to register daemon workers to a specific project. Each token is long-lived and should be treated like a service account credential.

`project tokens list`

rensei project tokens list [--project <slug>] [--json]

Example output:

ID              CREATED       LAST USED      STATUS
tok-abc123      2025-06-01    2 hours ago    active
tok-def456      2025-09-14    14 days ago    active

`project tokens create`

Create a new project token.

rensei project tokens create [--project <slug>]

The full token value (rsp_live_*) is shown exactly once. Copy it immediately and store it in your secret manager. It is used with rensei host install --project <slug> to register the local daemon.

`project tokens revoke`

Permanently revoke a project token. Any daemon registered with the revoked token will stop receiving work immediately.

rensei project tokens revoke <token-id> [--yes]

Sandbox allow-list

rensei project allow <project-slug-or-id>

Adds the named project to the local daemon's allow-list so the daemon accepts work from that project. This is typically set automatically during rensei host install --project <slug>. Use project allow if you need to manually add a project after the fact.

Global flags

Flag	Description
`--project <slug>`	Target a specific project instead of the active one
`--org <slug>`	Target a specific org
`--json`	Emit machine-readable JSON output
`--no-interactive`	Disable prompts for CI/non-TTY use

See Global flags for the full set.

Org - org-level membership, invites, and API keys
Linear integration - OAuth scopes, AgentSession lifecycle, webhook setup
Host daemon - register the local daemon to a project with host install
Sandbox providers - capacity pools - pool assignment and substrate resolution
Auth - API keys - rsk_live_* vs rsp_live_* token shapes

On this page