Miren
pilotctl appstore install io.pilot.miren About Miren
Miren is a deployment platform for small teams. This app is the app-store front door for the miren CLI, letting an agent drive a Miren PaaS over IPC.
What an agent gets: - Deploy lifecycle — miren.deploy (non-interactive build + deploy), miren.deploy.analyze (detect the stack/services without building), and miren.rollback. - Inspect apps — miren.apps, miren.app (status), miren.app.history, and miren.logs (JSON). - Server & diagnostics — miren.server.install/miren.server.status, miren.doctor, miren.whoami, and miren.debug.connection/miren.debug.advertise. - Full CLI surface — miren.exec runs any verbatim miren argv (addon, auth, env, route, cluster, disk, sandbox, and more).
Good to know: - Structured JSON is returned wherever the CLI offers it (e.g. pass --json). - Discover the live surface at runtime with miren.help — every method, its parameters, and its latency class (fast / med / slow). - Server-side commands need a configured cluster; without one, calls return a structured error ({stdout,stderr,exit}) telling the agent what to do next. - Runs on macOS and Linux (arm64 + amd64); the miren CLI is staged and sha-pinned on install.
Methods · 15
miren.exec miren.apps miren.app miren.app.history miren.logs miren.deploy miren.deploy.analyze miren.rollback miren.doctor miren.whoami miren.server.install miren.server.status miren.debug.connection miren.debug.advertise miren.help Full usage demo
When you need to operate a Miren PaaS from an agent — deploy or roll back apps and inspect their status, history, and logs — over IPC.
pilotctl appstore call io.pilot.miren miren.apps '{}'{"stdout":"[{\"name\":\"web\",\"status\":\"running\"}]","exit":0}Needs a configured cluster; if none is set up, output is a structured {stdout,stderr,exit} error telling you what to do next.
Worked examples
pilotctl appstore call io.pilot.miren miren.app '{"name":"web"}'{"stdout":"...status...","exit":0}pilotctl appstore call io.pilot.miren miren.logs '{"app":"web"}'{"stdout":"[{\"ts\":...,\"msg\":...}]","exit":0}pilotctl appstore call io.pilot.miren miren.deploy '{}'{"stdout":"...deployed...","exit":0}Non-interactive (--force); deploys the CURRENT working directory.
pilotctl appstore call io.pilot.miren miren.rollback '{}'{"stdout":"...rolled back...","exit":0}pilotctl appstore call io.pilot.miren miren.exec '{"args":["env","list","--app","web","--json"]}'{"stdout":"{...}","exit":0}Good to know
- Server-side commands need a configured cluster; without one they return a structured {stdout,stderr,exit} error explaining the next step — not a crash.
- miren.deploy builds and deploys the app in the CURRENT directory non-interactively (--force).
- Interactive/long-running subcommands (app run, login, server start) aren't usable over IPC — use the curated methods instead.
- Pass --json inside miren.exec args wherever the subcommand supports it to get structured output.
- server install / server status are Linux-only.
Next
io.pilot.miren miren.help '{}'
What’s New
- Operate the Miren PaaS from an agent: deploy and roll back apps; inspect status, logs, and history; run the server; and diagnose connectivity — plus a passthrough exec for any miren subcommand.
