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 invited email address and your existing AMP LAB password. Renewing access does not change your password. If it is not accepted, choose Forgot Password? on the secure sign-in screen.
Prefer a security key? Choose Sign in with Passkey on the secure AMP LAB sign-in screen.
Using a private computer? Select Remember me on the secure sign-in screen. AMP LAB will restore your session after a refresh without storing your password in this page.
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.
PRIVATE GITHUB WORKSPACE
Use the normal development workflow.
AMP LAB creates one private repository for this active grant. Controlled-core grants receive only approved source; new-effect grants receive only a generated public-SDK starter and no owner source. Protected main stays current until access ends.
- Accept the private repository invitation from GitHub.
- Clone it and open the folder in Codex or your editor.
- Create a branch and make your change.
- For local testing, sign in to the normal AMP LAB app and open the cloned project under Partner development. The repository's signed scope activates automatically on Windows or macOS.
- Choose Build and reload after every edit. AMP LAB loads the changed approved audio, code, UI and data as one temporary DEV preview; the released version is never overwritten.
- Repeat local tests and rebuilds until satisfied, then Restore the release and open a pull request. AMP LAB runs the server-side scope gate automatically for owner review.
No MCP server, token, custom Codex prompt, or installer rebuild is required. AMP LAB owns the scoped preview toolchain. UI/data reloads take seconds; compiled changes use the isolated signed builder with a three-minute limit. Owner approval is required before anything can enter the product.
CONTINUE WITH YOUR AI
Connect your AI to the approved repository.
Copy one setup prompt for ChatGPT/Codex or Claude. It prepares the exact private repository on the local computer and stops before development begins.
- Accept and clone from GitHub. Open the approved repository, accept its invitation, then use GitHub’s Code → Open with GitHub Desktop or
git cloneto create a local folder. - Select the cloned folder as your AI project. In Codex, choose Add project and select the cloned repository root—the folder containing
.git,AGENTS.md, and.amplab. For Claude Code, start it from that folder. - Do not select the local AMP LAB URL as a project.
http://127.0.0.1:18321is the running AMP LAB service address, not a folder. - Start AMP LAB, then copy the setup prompt. Paste it into the task opened for that repository. The AI will verify the repository and connect it to local AMP LAB.
- Wait for “Workspace ready.” Give the AI your development requirements only after both GitHub and AMP LAB checks pass.
Two different locations are used. The cloned GitHub folder is the Codex/Claude project. http://127.0.0.1:18321 is only AMP LAB’s fixed local service address on Windows and macOS. No installation path, Registry entry, environment variable, or MCP connection is needed. The AI uses the local Partner Development API at this address to open the signed repository, run Build and reload, verify the temporary DEV effect, and restore the released version. This local DEV deployment never publishes or overwrites the released product.
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.