メニュー
First-time setup for the Durable Agents stack (Mastra + Trigger.dev). Run once before using the main skill.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/modbender/skill-library-mcp --skill durable-agents-setupコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
Bloom Mission Discovery — find missions matched to your taste, submit content, and track rewards. Powered by Bloom Protocol.
DESCRIPTION of what this skill does. Include specific trigger keywords and scenarios. Use when: scenario1, scenario2, scenario3.
Read/search Gmail via gog CLI. Inbox check, email search, content retrieval.
SKILL.md を表示中
| name | durable-agents-setup |
| description | First-time setup for the Durable Agents stack (Mastra + Trigger.dev). Run once before using the main skill. |
Runs once. After setup is verified, remove the setup reference block from SKILL.md.
These apply for the entire setup without exception.
package.json are pinned intentionally. If a version mismatch appears to be the problem, the fix is in the configuration — not in bumping or changing a dependency../setup.sh — unless the recovery section says otherwise.Before doing anything, verify the stack is not already up.
curl -s http://localhost:3000/health
If this returns {"status":"ok",...}, the stack is already running. Skip to the Post-Setup Checklist and confirm all checks pass. If they do, setup is complete — do not re-run anything.
If the API is not up, check whether the containers exist but are stopped:
cd trigger-infra && docker compose -p trigger ps
If containers exist but are stopped, bring them back up:
docker compose -p trigger up -d
cd ..
npm run dev
Then re-run the health check. Only proceed to Step 1 if no prior setup exists.
git clone https://github.com/ainakwalamonk/durableclaw.git
cd mastra-triggers-openclaw
./setup.sh
Handles: deps, Docker infra, Trigger.dev bootstrap (user, org, project, secret key, project ref, CLI token), database creation, migrations, AI provider config, smoke tests.
If it fails at any stage, go to the matching recovery section below. Fix it, then resume manually from that step.
Start the worker first (separate terminal), then run the test:
npm run trigger:dev # keep running
npm run trigger:test # in another terminal
trigger:test fires dummy-task via the Trigger.dev API and polls for completion. Pass = full Trigger.dev pipeline is working.
npm run dev
curl http://localhost:3000/health
Expected: {"status":"ok","timestamp":"..."}
Do not hardcode or guess LLM credentials. Read them from the openclaw project on this machine.
Check in this order until you find the values:
gateway/.env, gateway/config.json, docker-compose.yml service named gateway, or any .env at the project root that contains AI_BASE_URL, AI_API_KEY, or MODEL_ID).openclaw.config.json, config/openclaw.json, or any JSON referencing model/provider settings).docker ps --format '{{.Names}}\t{{.Ports}}' | grep -i gateway
docker inspect <container_name> --format '{{json .Config.Env}}'
Once you have AI_BASE_URL, AI_API_KEY, and MODEL_ID, write them to .env in this project:
sed -i '' "s|^AI_BASE_URL=.*|AI_BASE_URL=<value>|" .env
sed -i '' "s|^AI_API_KEY=.*|AI_API_KEY=<value>|" .env
sed -i '' "s|^MODEL_ID=.*|MODEL_ID=<value>|" .env
Run the infrastructure smoke test:
npm run trigger:test
Expected: dummy-task completes with status COMPLETED. This test makes no LLM call — a pass here means the full Trigger.dev pipeline is operational.
If Step 6 failed to find real LLM credentials and .env is missing AI_BASE_URL, AI_API_KEY, or MODEL_ID, fill them with placeholders only for this test so the worker starts:
grep -q "^AI_API_KEY=" .env || echo "AI_API_KEY=placeholder" >> .env
grep -q "^AI_BASE_URL=" .env || echo "AI_BASE_URL=http://placeholder.local/v1" >> .env
grep -q "^MODEL_ID=" .env || echo "MODEL_ID=placeholder-model" >> .env
Then re-run npm run trigger:test. Placeholders are only acceptable here — Step 8 requires real credentials. If you used placeholders, resolve the LLM config from the openclaw gateway before continuing.
If the smoke test fails, the problem is in the infrastructure — go to the Recovery section. Do not debug LLM credentials until this passes.
Once real LLM credentials are in .env from Step 6:
curl -X POST http://localhost:3000/pipeline \
-H "Content-Type: application/json" \
-d '{"prompt": "Build a URL shortener service"}'
Expected: JSON with plan, review, and run IDs.
Open http://localhost:3040 and confirm the run appears.
docker info
macOS:
brew install --cask docker
# Open Docker Desktop and wait for it to start
Linux:
sudo apt-get update && sudo apt-get install -y docker.io docker-compose-plugin
sudo systemctl start docker
sudo usermod -aG docker $USER && newgrp docker
Re-run ./setup.sh after Docker is running.
cd trigger-infra && docker compose -p trigger ps
docker logs trigger-webapp-1
docker logs trigger-postgres-1
If containers are unhealthy:
cd trigger-infra && docker compose -p trigger down -v
cd .. && ./setup.sh
until pg_isready -h localhost -p 5433 -U postgres 2>/dev/null; do sleep 2; done
echo "Postgres ready"
bash trigger-infra/init-trigger.sh
If it fails to find the magic link:
docker logs trigger-webapp-1 2>&1 | grep magic
If that returns nothing, pull the key directly from the DB:
docker exec trigger-postgres-1 psql -U postgres -d postgres -t -A \
-c "SELECT \"apiKey\" FROM \"RuntimeEnvironment\" WHERE type = 'DEVELOPMENT' LIMIT 1"
Write the result to .env:
TRIGGER_SECRET_KEY=<value>
The CLI requires the externalRef — not the project name or slug.
docker exec trigger-postgres-1 psql -U postgres -d postgres -t -A \
-c "SELECT \"externalRef\" FROM \"Project\" LIMIT 1"
Write the result to two places:
.env → TRIGGER_PROJECT_REF=<value>trigger.config.ts → replace the project: fieldThe CLI (v3.3.17) reads ~/Library/Preferences/trigger/default.json on macOS.
cat ~/Library/Preferences/trigger/default.json 2>/dev/null
cat ~/Library/Preferences/trigger/config.json 2>/dev/null
If the self-hosted profile is missing or has a placeholder token:
PAT=$(grep TRIGGER_ACCESS_TOKEN .env | cut -d= -f2)
node -e "
const fs = require('fs');
const p = process.env.HOME + '/Library/Preferences/trigger/default.json';
let cfg = {};
try { cfg = JSON.parse(fs.readFileSync(p, 'utf8')); } catch {}
cfg['self-hosted'] = { accessToken: '$PAT', apiUrl: 'http://localhost:3040' };
fs.writeFileSync(p, JSON.stringify(cfg, null, 2));
console.log('Updated.');
"
Verify:
npx trigger.dev@3.3.17 whoami --profile self-hosted
Expected:
◇ Account details [self-hosted]
│ Email: admin@trigger.local
│ URL: http://localhost:3040
Fallback — authenticate interactively:
npx trigger.dev@3.3.17 login -a http://localhost:3040
Or override via env var for CLI commands:
export TRIGGER_ACCESS_TOKEN="<your-pat>"
The PAT in the database was inserted with bad encryption — a known bug in init-trigger.sh. Regenerate it:
# Generate and encrypt a new PAT
node -e "
const crypto = require('node:crypto');
const ENCRYPTION_KEY = '400852556fef3f19b9d0dfb558eb10f5';
const token = 'tr_pat_' + crypto.randomBytes(20).toString('hex');
const nonce = crypto.randomBytes(12);
const cipher = crypto.createCipheriv('aes-256-gcm', ENCRYPTION_KEY, nonce);
let enc = cipher.update(token, 'utf8', 'hex') + cipher.final('hex');
const tag = cipher.getAuthTag().toString('hex');
const hash = crypto.createHash('sha256').update(token).digest('hex');
console.log(JSON.stringify({ token, nonce: nonce.toString('hex'), ciphertext: enc, tag, hash }));
" > /tmp/new_pat.json && cat /tmp/new_pat.json
# Insert into DB
TOKEN=$(node -e "console.log(require('/tmp/new_pat.json').token)")
NONCE=$(node -e "console.log(require('/tmp/new_pat.json').nonce)")
CIPHER=$(node -e "console.log(require('/tmp/new_pat.json').ciphertext)")
TAG=$(node -e "console.log(require('/tmp/new_pat.json').tag)")
HASH=$(node -e "console.log(require('/tmp/new_pat.json').hash)")
USER_ID=$(docker exec trigger-postgres-1 psql -U postgres -d postgres -t -A -c "SELECT id FROM \"User\" LIMIT 1")
docker exec trigger-postgres-1 psql -U postgres -d postgres -c "
DELETE FROM \"PersonalAccessToken\" WHERE name = 'cli-auto';
INSERT INTO \"PersonalAccessToken\" (id, name, \"userId\", \"obfuscatedToken\", \"encryptedToken\", \"hashedToken\", \"createdAt\", \"updatedAt\")
VALUES ('pat_$(openssl rand -hex 12)', 'cli-auto', '$USER_ID',
'tr_pat_****...', '{\"nonce\": \"$NONCE\", \"ciphertext\": \"$CIPHER\", \"tag\": \"$TAG\"}'::jsonb,
'$HASH', NOW(), NOW());
"
# Update CLI config
node -e "
const fs = require('fs');
const p = process.env.HOME + '/Library/Preferences/trigger/default.json';
let cfg = {};
try { cfg = JSON.parse(fs.readFileSync(p, 'utf8')); } catch {}
cfg['self-hosted'] = { accessToken: '$TOKEN', apiUrl: 'http://localhost:3040' };
fs.writeFileSync(p, JSON.stringify(cfg, null, 2));
console.log('Done');
"
# Write to .env
sed -i '' "s|^TRIGGER_ACCESS_TOKEN=.*|TRIGGER_ACCESS_TOKEN=$TOKEN|" .env
The SDK and CLI are pinned to 3.3.17 to match the self-hosted v3 platform. Do not change the versions. Fix the config instead.
Verify the CLI version:
npx trigger.dev@3.3.17 --version
If package.json has ^3.3.17 (with caret), remove the caret so it reads exactly:
"@trigger.dev/sdk": "3.3.17",
"trigger.dev": "3.3.17"
Then:
npm install
docker exec trigger-postgres-1 psql -U postgres -c "CREATE DATABASE mastra;"
npm run db:migrate
Set in .env:
AI_BASE_URL=<provider base URL>
AI_API_KEY=<key>
MODEL_ID=<model id>
Common values:
AI_BASE_URL=https://api.openai.com/v1AI_BASE_URL=https://openrouter.ai/api/v1AI_BASE_URL=http://localhost:11434/v1, AI_API_KEY=ollamaThis project uses ESM. import statements are hoisted above all code execution, including dotenv.config(). Any module that reads env vars at the top level will fail if loaded statically before .env is parsed.
Fix: all run/test commands use --env-file=.env (already in package.json). Do not remove that flag.
Trigger.dev v3 bundles code for the worker. External .md files are not bundled by default — fs.readFileSync on AGENT.md will throw ENOENT in the worker.
Fix: embed agent instructions as a string constant directly in the agent's .ts file. Do not use fs.readFileSync for agent instructions.
| Path | Purpose |
|---|---|
src/config/model.ts | Model singleton. Requires AI_BASE_URL, AI_API_KEY, MODEL_ID. |
src/agents/{name}/ | Each agent: {name}.ts with embedded instructions. |
src/tools/ | Shared tools. |
src/pipelines/ | Pipeline orchestrators chaining Trigger.dev tasks. |
src/pipelines/tasks/ | Durable tasks — one agent call per task. |
src/mastra/index.ts | Central agent registry. |
src/trigger/index.ts | Exports all tasks for the worker. |
src/app/index.ts | Express API: /health and /pipeline. |
trigger-infra/ | Docker Compose stack + bootstrap script. |
trigger.config.ts | Trigger.dev project config (v3). |
scripts/test-trigger.ts | Infrastructure verification script. |
db/migrations/ | SQL migrations (tracked). |
| Command | What it does |
|---|---|
npm run dev | Express API (port 3000) + Trigger.dev worker concurrently |
npm run app:dev | Express server only |
npm run trigger:dev | Trigger.dev worker only |
npm run trigger:test | Fire dummy-task and verify completion (no AI needed) |
npm test | Smoke tests |
npm run db:migrate | Run database migrations |
| Variable | Source |
|---|---|
TRIGGER_SECRET_KEY | Auto-extracted from DB by setup |
TRIGGER_PROJECT_REF | Auto-extracted from DB by setup |
TRIGGER_ACCESS_TOKEN | Auto-generated PAT by setup |
TRIGGER_API_URL | Default http://localhost:3040 |
DATABASE_URL | Default postgres://postgres:postgres@localhost:5433/mastra |
AI_BASE_URL | Set during setup |
AI_API_KEY | Set during setup |
MODEL_ID | Set during setup |
cd trigger-infra && docker compose -p trigger down
Data persists. Next up -d resumes from current state. Never use -v unless deliberately wiping everything to re-run ./setup.sh.
npm run trigger:test passes (infrastructure smoke test — no AI needed)curl http://localhost:3000/health returns ok.env match the openclaw gateway configplan, review, and run IDsnpm test passesRemove the setup reference block from SKILL.md. Setup is complete.