Hosted runtimeServe static apps or app-owned server code.
Managed dataAdd persistent storage when the app needs it.
Private appsOTP, identity provider, or service token.
curl -fsSL https://tmrwrun.com/install.sh | bash
Set up tmrw.run for this workspace, then start the first-app onboarding conversation.
Follow these steps in order:
1. Install or update the tmrw.run CLI:
curl -fsSL https://tmrwrun.com/install.sh | bash
2. Install or update the tmrw.run Codex skill:
SKILL_HOME="${CODEX_HOME:-$HOME/.codex}/skills/tmrw-run"
mkdir -p "$SKILL_HOME"
curl -fsSL https://tmrwrun.com/skills/tmrwrun/SKILL.md -o "$SKILL_HOME/SKILL.md"
If this agent cannot install local skills, download https://tmrwrun.com/skills/tmrwrun/SKILL.md, read it, and follow it for this session.
3. Ask the user for an API key from https://tmrwrun.com/dashboard. Use a secure secret input mechanism if one exists. Do not write the key into source files, browser code, committed files, screenshots, logs, or generated documentation.
4. Store the key locally using the safest available option:
- For one-off work, export it only in the current shell/session.
- For project-local work, use .env.local only if it already exists or can be created with .gitignore protection.
- Before writing .env.local, verify .gitignore excludes it.
- If neither option is appropriate, ask the user where to store the key.
5. Set the endpoint and key for the working shell:
export TMRW_RUN_API_URL=https://api.tmrwrun.com
export TMRW_RUN_API_KEY=tmrw_...
6. Verify access before deploying:
curl -fsS "$TMRW_RUN_API_URL/v1/sites" -H "authorization: Bearer $TMRW_RUN_API_KEY" >/dev/null
Stop and report the error if verification fails.
7. After verification passes, say setup is complete and ask the user which path to take:
- Create and deploy a new todo app.
- Inspect this existing app and deploy it only if it already fits.
- Inspect this existing app and report required compatibility changes only.
- Stop after setup.
If the user chooses the todo app path, ask for the target directory and confirm exactly what you will create before writing files. Build a small polished todo app, run its build checks, deploy it with tmrw.run, and report the final URL.
If the user chooses an existing app path, inspect first. Identify the stack, build command, output directory, runtime shape, and whether it is deployable as-is. Do not modify, refactor, or deploy until the user explicitly approves the next step.
Use the installed tmrw.run skill for product-specific deploy, access, storage, and deletion commands.
Safety rules:
- Inspect before changing.
- Ask before creating files for a new app.
- Ask before modifying an existing app.
- Never refactor an app to fit tmrw.run without explicit user approval.
- Prefer the smallest compatibility change that preserves the user's stack and intent.