Mechanic now has a developer workflow for teams who want to manage tasks closer to their code, editors, AI tools, CI, and monitoring systems.
With API tokens, the Mechanic CLI, and the task sync API, you can pull tasks into local files, edit them in your own tools, preview changes safely, review diffs, and publish back to Mechanic when you're ready.
You can also monitor shop queue health from outside the app.
mechanic shop status --json
and the shop status API report waiting runs, running runs, queue lag, and the top tasks, actions, or event topics contributing to the wait. Use that with tools like Cronitor, UptimeRobot, Better Stack, Datadog, New Relic, or your own monitoring system.What's new
- Local task projects with mechanic init
- Pull tasks into Git-friendly JSON files with mechanic tasks pull
- Create new local tasks with mechanic tasks new
- Edit Liquid, docs, subscriptions, and task settings locally
- Preview local task changes without saving them
- Diff local changes against the current Mechanic version
- Publish task changes intentionally
- Monitor shop queue health and queue lag
- Optional GitHub Actions templates for validation, deploys, and sync-back
- Better support for AI coding agents working with Mechanic tasks
How to use it
npm install -g @lightward/mechanic-cli
mechanic init --shop example.myshopify.com
mechanic tasks pull
mechanic tasks preview order-tagger
mechanic tasks diff order-tagger
mechanic tasks publish order-tagger
Monitor queue health
mechanic shop status
mechanic shop status --json
Or call the API endpoint directly with a Mechanic API token:
curl https://api.mechanic.dev/v1/shop/status \
-H "Authorization: Bearer $MECHANIC_API_TOKEN"
Learn more
- Local task development with the Mechanic CLI: https://learn.mechanic.dev/resources/mechanic-cli
- API tokens and task sync API: https://learn.mechanic.dev/resources/mechanic-cli/mechanic-task-sync-api
- Monitoring Mechanic: https://learn.mechanic.dev/techniques/monitoring