Try this on day one: review store deployment setup
“Review our store project’s deployment history and scheduled deployments, then summarize its current setup.”
- Deployment history summary
- Scheduled deployments
- Current project setup
Your bots review deployment history and server settings, then update project configuration or build commands with your approval. New bots start on Ask, so they check with you before they act in DeployHQ, except on Hermes and other ACP engines.
Free app. DeployHQ connects through Flux Router credits or your own connected-apps key. You sign in to DeployHQ yourself.
Review our store project’s deployment history and scheduled deployments, then summarize its current setup.
You signed in to DeployHQ once. Your Chief put a bot on it.
Waiting on you · Ask mode
Next step: update project settings or build commands in DeployHQ. Go ahead?
“Asks first” means the bot checks with you before it does that, on Ask, the mode every new bot starts in. You can give a bot more freedom later. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about, and Hermes doesn’t ask before connected-app tools, so these actions don’t ask first there.
Try this on day one: review store deployment setup
“Review our store project’s deployment history and scheduled deployments, then summarize its current setup.”
Tell your Chief of Staff what you want done in DeployHQ, in plain words. It builds a team for the job, starting from the closest one in the library, and shows you who is on it before anyone starts.
Free for Mac, Windows and Ubuntu. Pick the AI you already use; if it needs installing, Murage opens a one-line command for you.
Open connected apps and sign in to DeployHQ once. It runs through Flux Router credits, or your own connected-apps key.
Tell your Chief of Staff what to do with DeployHQ. New bots start on Ask, so they check with you before they act, except on Hermes and other ACP engines.
What a team adds here
Your team reads what shipped or broke and writes it up for the people who need to know.
Works across your apps
One brief can pull from DeployHQ, your calendar, your CRM and the web, then hand you one answer.
Keeps notes on your business
Your bots keep notes on your customers, your tone and how you like things done, stored on your computer where you can open and edit them.
Runs on the AI you already pay for
Claude Code, Codex, Hermes, a model key or a local model. The Murage app is free; your AI provider bills you as usual.
Yes. Sign in to DeployHQ once inside Murage, through Flux Router credits or your own connected-apps key, and your bots can read projects, deployment history, and scheduled deployments.
Not while it’s on Ask, where every new bot starts: it checks with you before it acts in DeployHQ. On Auto or Full access, replies in an existing conversation and routine edits go ahead, but a bot still stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. Only No limits turns that off. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about, and Hermes doesn’t ask before connected-app tools.
The Murage app is free. DeployHQ connects through Flux Router credits, or your own connected-apps key if you have one. Your AI provider bills you as usual.
DeployHQ and the other product names and logos on this page are trademarks of their respective owners. Murage is not affiliated with or endorsed by them; the names and logos are used only to identify the apps and engines Murage works with.
Download the free app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
No account needed · Runs on the AI plan you already pay for