INVITED PARTNER WORKSPACE
Make the sound better.
Open the areas AMP LAB has shared with you, develop with your own Codex subscription, and send finished work back for review.
Your development access is approved
Continue to AMP LAB's secure sign-in with your invited email and password. If your invitation included a one-time password, you will choose a new password before your workspace opens.
Sign in to your workspace
Use the email address and password supplied with your invitation.
Prefer a security key? Choose Sign in with Passkey on the secure AMP LAB sign-in screen.
Checking your sign-in…
YOUR DEVELOPMENT AREAS
Choose where to begin.
AMP LAB automatically opens the exact kind of workspace your invitation allows.
MUSICIAN PARTNER
Guided development is ready AMP LAB will keep the workflow in plain language and handle technical setup automatically.
PRIVATE AI CORE WORKSPACE
Tell AMP LAB what you want to change.
Your private coding agent can see only this approved area. Source and patches remain inside AMP LAB.
YOUR DEVELOPMENT PACKAGE IS READY
Double-click the downloaded AMP LAB Developer Package.
The installed AMP LAB application verifies your access, extracts only the areas shared with you, starts Multi-FX, and opens the approved folder as a Codex project. There are no tokens or settings to copy.
CODEX CONNECTION
AMP LAB sets it up. You approve one secure sign-in.
The package verifies and trusts the exact approved folder, pre-registers amp_lab_core as disabled outside approved workspaces, enables it for this project, and opens the project in Codex. Never add a server URL or copy a token.
In an empty composer, run /mcp. This opens a read-only status list; the rows are not a menu. Find the exact row amp_lab_core. Enabled plus Authenticated (OAuth) means it is connected. If the new row is not visible yet, open Settings > Plugins > MCPs, select Restart once, and reopen the project. If it offers Authenticate, approve the sign-in with the same invited partner account. A row named only amp_lab with the partners…/mcp URL is a different extension workflow and does not authorize core-source work.
Do not use Settings > Connections. That page controls remote devices and does not show project MCP servers.
- Double-click the downloaded .amplabdev file.
- AMP LAB verifies and extracts your approved workspace, then opens that exact folder as a project in Codex.
- The package registers this verified folder as a trusted Codex project so its project-scoped amp_lab_core server can load.
- In an empty task composer for that project, run /mcp. Do not try to select a row: this is the status panel.
- Find the exact row amp_lab_core — not amp_lab. If offered, choose Authenticate and approve the one-time partner sign-in. It is ready when amp_lab_core shows Enabled and Authenticated (OAuth).
- Start a fresh task in the same project and paste the completed prompt below.
Returning later? Continue in the existing Codex workspace on your computer. Use “Download package again” only if you need another copy of its .amplabdev launcher.
CODEX — YOUR FIRST PROMPT
Complete these two checks before copying
The prompt stays locked until the connection is ready and your request is specific. This prevents Codex from starting without AMP LAB tools or receiving placeholder text.
LISTENING REVIEW
Compare your candidate
Listen at the same level before choosing.