Work Across Every App
Clone and run any app in your org from one agent session.
One org connection (https://www.stardeck.ai/api/mcp) reaches every app in your organization. Your agent can clone and run any of them, so a change that spans several apps happens in one session. You don't add a connection per repo.
Requirements
- An org AI connection in your agent. See Connect Your AI Tool.
- The connection bound to a role with Repository access (
agent:repos:write), authorized at Read & write. See Tools & Permissions. - Git and Node on your machine.
- Agent development enabled on each app. It's on by default for every app.
Pull an app
Ask your agent:
Clone our storefront app here so we can work on it.
It calls get_repo_access, gets a clone URL with a token, and runs git clone on the default branch. Repeat for each app, then open the checkouts in one workspace (a parent folder works).
The token lasts about an hour. If a later git push or pull fails to authenticate, ask for repo
access again and update the remote, or use your own GitHub access for the
remote.
Run an app
Set up the storefront to run locally and start it.
Your agent calls get_project_dev_env, writes the result to .env.local, installs dependencies, and starts the dev server. The env includes the deployment identity and secret, the sandbox database URL, the control-plane URL, data-store connections, and custom env vars.
This is the app's sandbox environment. On a new app the sandbox still shares production's data
until you split them. .env.local holds real secrets and is git-ignored. Never commit it.
For the single-app CLI flow (stardeck env pull), see Run Your App Locally.
Ship changes
Same rules as one app, per repo. The token pushes only to agent/** and starcat/** branches, so open a pull request into main for each app. The cloud sandbox doesn't pull your pushes by itself (load a commit from Git History). See Working alongside the Stardeck agent.
The System Map shows which app calls which and what reads which data store.