Origin Docs

Studio Quickstart

Create your first ORGN Studio project, deploy a confidential workspace, and start an AI-assisted development session in minutes.

This guide walks you through signing in with id-orgn, creating your first project, deploying a confidential workspace, and starting work in a chat session at /chat/:id.

ORGN Studio is mission control for repository-backed projects — not a web clone of ORGN CDE. Every project is a deployed workspace created from a Git repository (or template), provisioned inside a TDX Trust Domain, indexed for context, and prepared for agent-driven development. See ORGN Studio overview for when to use Studio vs the desktop IDE.

Sign in with id-orgn

Open ORGN Studio and choose Sign in with ORGN SSO.

Authentication is handled by id-orgn (id.orgn.com) — the shared identity provider for CDE, Studio, Gateway, and Scanner. Sign in with GitHub is available on the id-orgn login page, along with passkeys and other linked providers. For private repository import, you may also need to connect the ORGN GitHub App from project settings.

After authentication you land on the Projects page. If this is your first visit, the workspace is empty and shows Import New Project.

Create a new project

You can start from an existing repository or a template.

Option A: Import a repository

From Import New Project, select a repository you have access to:

  • Search by repository name
  • Choose a branch (default is usually main)

ORGN creates a project-scoped clone inside your confidential workspace — a live Git working copy connected to GitHub, not a frozen snapshot. The upstream repository is not modified unless you explicitly open a pull request or push changes.

Won't my repo go stale? Two different things:

Git (your source files) — When you start a new task or worktree, ORGN fetches the latest base branch from GitHub before creating an isolated branch checkout. You work on a fresh branch; completed work returns via pull request or push. The sandbox does not auto-pull on every upstream commit, but new work always starts from a current fetch.

Code index (agent context) — On import and deploy, ORGN automatically builds a codebase index (a Repomix snapshot agents use for repository-wide context). The index is tied to a commit SHA. After large changes on GitHub or in the sandbox, re-index manually from the project Dashboard (Re-Index) or Settings → Context → Refresh. Re-indexing updates agent context only — it does not change your Git files.

See Project context — code index.

Option B: Use a template

Templates provide preconfigured starter projects (Next.js, SaaS boilerplates, demos). Selecting a template creates a new repository instance inside ORGN that behaves like an imported project after deployment.

Configure the workspace

After selecting a repository or template, configure the workspace:

  • Repository name and owner
  • Visibility (private or public)
  • Environment variables (optional)

All workspaces run inside Intel TDX Trust Domains by default — hardware-backed confidentiality, not a policy promise.

Add runtime secrets such as DATABASE_URL or JWT_SECRET during setup or later from Settings → Secrets. Secrets are injected at runtime and are never committed to Git.

Deploy the project

Click Deploy. ORGN provisions the environment in real time:

  • Creates the project container
  • Clones the repository
  • Installs dependencies
  • Indexes the codebase
  • Prepares the agent runtime

When deployment completes, the project card shows a running workspace with indexing complete and agents ready.

Open the project dashboard

Click the project card to enter the project dashboard. From here you can:

  • Manage tasks and milestones
  • Run discovery with AI over the indexed repository
  • Track open pull requests
  • Create or continue worktrees (isolated agent sessions)

If the workspace is stopped, restart it from the project view.

Start your first chat session

Worktrees are the core working units in Studio. When you create or select a task, ORGN opens a browser workspace at:

/chat/:id

Inside a worktree:

  • The agent has access to the indexed repository
  • All execution runs inside the provisioned Trust Domain
  • Changes are isolated to a session branch
  • You interact with the agent via chat

Type @ in the chat input to attach a specific file. Example prompts:

  • "Add JWT authentication to the API."
  • "Create integration tests for the payment flow."
  • "Explain how the caching layer works."

Review changes

File modifications appear in the Changes panel. Before creating a pull request:

  • Review diffs line by line
  • Run tests in the integrated terminal
  • Validate agent edits

Changes stay on the worktree branch until you explicitly promote them. Nothing is pushed to Git automatically.

Using ORGN CDE (desktop)

The same projects, tasks, agents, and worktrees are available in ORGN CDE — the native desktop app for macOS and Windows. Sign in with id-orgn, then choose Open Cloud Project or Open Project.

See CDE Quickstart for install and first-session details. Launching desktop CDE directly from a Studio task is marked Soon.

Next steps

On this page