Skip to main content

← All use cases

K. Ephemeral agent runtimes

Sandbox-per-PR preview deployment

A reviewer agent provisions a throwaway storage bucket plus Postgres tied to a PR number, seeds it from a snapshot, and the whole thing is torn down when the PR closes.

Prompt for any LLM (no setup needed)

Paste this into ChatGPT, Claude, or Gemini — no MCP, no API key, no install:

Read https://instanode.dev/llms.txt for the API.

I want to: a reviewer agent provisions a throwaway storage bucket plus Postgres tied to a PR number, seeds it from a snapshot, and the whole thing is torn down when the PR closes.

Write a complete runnable script (bash + whatever language fits) that: - Provisions the services I need (Postgres + S3-compatible storage + container deploy) from instanode.dev - Does the work above end-to-end - Prints expected output at each step - Tells me how to claim the resources at the end if I want to keep them past 24 hours

Use real curl commands against api.instanode.dev. Quote the actual response shapes from llms.txt. ```

Sample agent prompt

On every PR opened against this repo, provision an isolated Postgres + S3-compatible bucket via instanode.dev, restore from the staging snapshot (s3://staging/snapshot.dump), and deploy the app container to pr-NNN.instanode.dev. On PR close, hit the delete endpoint for each resource. Pass the share URL back as a PR comment.

Steps to follow

  • Step 1: Provision Postgres and S3-compatible storage for PR #42.

``bash PR=42 DB=$(curl -sX POST https://api.instanode.dev/db/new -H 'Content-Type: application/json' -d '{"name":"sandbox-per-pr-preview-deployment-db"}') BUCKET=$(curl -sX POST https://api.instanode.dev/storage/new -H 'Content-Type: application/json' -d '{"name":"sandbox-per-pr-preview-deployment-storage"}') echo "$DB" > .preview/pr-$PR-db.json echo "$BUCKET" > .preview/pr-$PR-bucket.json ``

  • Step 2: Seed Postgres from snapshot.

``bash pg_restore --clean --if-exists \ -d "$(jq -r .connection_url .preview/pr-$PR-db.json)" \ snapshots/staging.dump ``

  • Step 3: Mirror seed assets into the new bucket.

``bash aws s3 sync s3://staging/fixtures/ \ s3://$(jq -r .bucket .preview/pr-$PR-bucket.json)/ \ --endpoint-url https://s3.instanode.dev ``

  • Step 4: Deploy the app.

``bash curl -X POST https://api.instanode.dev/deploy/new \ -H "Authorization: Bearer $INSTANODE_TOKEN" \ -F "name=pr-$PR-preview" \ -F "image=ghcr.io/me/app:pr-$PR" \ -F "subdomain=pr-$PR" ``

  • Step 5: On PR close, fan-out deletes — DELETE /api/v1/resources/:id per resource (using each resource's id from its provision response, with a Bearer session token). Anonymous-tier resources also auto-reap at the 24h TTL, so a missed delete is bounded.

Why this works on instanode.dev

One token per resource means GitHub Actions can pass three opaque strings instead of three sets of credentials. /storage/new and /db/new complete in a single second each, so the preview is ready before CI finishes its first test.