Pilot acts on its own inside the spec. When a goal can't be met inside it, Pilot does what it can, then asks: the exact change, the numbers, and what happens if the answer is no. An approval becomes a spec change under the approver's name, and Pilot acts within the new limits.
What Pilot can ask for
| Kind | Proposal | On approval |
|---|---|---|
cost_ceiling | a new max_monthly_cost_usd for one intent | the ceiling changes |
bounds | new [min, max] for one or more bounds | the bounds change |
objective | a new threshold for one objective | the objective changes |
create_types | resource types to allow | added to boundaries.create_types |
manage | all (or back to profiled) | boundaries.manage changes |
unprotect | names to remove from boundaries.protected | removed |
approve_operation | operations Pilot can't run itself, like deleting data | run once, as the approver |
other | a note | nothing changes; Pilot gets the answer |
No duplicate open requests, no re-asking within a day of a denial, at most six waiting. Unanswered requests expire after a week.
Changes that wait for approval
At level propose (an intent's level, or the default for resources your infrastructure code manages: https://infrapilot.fly/docs/manifest.md), every change Pilot wants to make arrives as an approve_operation request. It carries the exact operation (resource, property, old and new value), Pilot's reasoning, why it needs approval, the objectives it is for, and the estimated monthly cost before and after.
Approve it and the operation runs as written, in your name, behind the same checks and health gate as any change. If the resources changed after Pilot proposed it, the approval is refused, nothing runs, and Pilot proposes again against the resources as they are. Deny it and Pilot does not ask for the same change again for a day.
Answering
- Slack app: Approve and Deny buttons in the message. Recorded under the address on your Slack profile, which must be a member of the workspace.
- Email: a personal link to Approve or Deny, no sign-in. Recorded under that address.
- Phone: a text with a four-digit code. Reply
YES 4821orNO 4821(text after the code is kept as a note). Urgent requests can also call. - Slack or Teams webhook: a button that opens the request in the dashboard (sign-in required).
- Dashboard: the Requests page and the top of Overview.
First answer wins. Everyone is told the outcome.
Connectors
The Slack app
In Settings, choose Add to Slack, pick the channel Pilot should post to, and allow it. Slack posts a hello there. For a private channel, also type /invite @Infrapilot in it. A coding agent can't do this step: it needs a person signed in to both Slack and Infrapilot.
- One message per request, with the exact change, Pilot's reasoning, why it needs approval, the estimated monthly cost before and after, and Approve and Deny.
- Who can answer. Anyone in the channel can press a button; only members of the Infrapilot workspace are obeyed. Infrapilot asks Slack who pressed it and matches the email address on their Slack profile to a member (Settings, People). Anyone else is told, privately, that nothing changed and who the owner is. People from another Slack workspace in a shared channel are always refused.
- One thread per request. Once it is answered the buttons go, wherever the answer came from, and the thread says who answered and how, what happened when Pilot's engine ran it (applied, refused, or lapsed because the resources had changed), and later if that change was undone.
- Alerts and the first review are posted to the same channel as plain messages.
Add it again to post to a second channel. Removing it in Settings revokes Infrapilot's access to your Slack workspace, unless another channel or workspace of yours still uses it. What the app can see and do is in https://infrapilot.fly/docs/security.md.
Everything else
The owner's email is always included. Add more in Settings, or during setup:
curl -s -X POST $INFRAPILOT_URL/api/v1/setup/contacts \
-H "Authorization: Bearer $INFRAPILOT_TOKEN" -H "Content-Type: application/json" \
-d '{"email": ["team@example.com"], "phone": ["+14155550123"],
"slack_webhook": "https://hooks.slack.com/services/T000/B000/XXXX",
"teams_webhook": "https://example.webhook.office.com/webhookb2/..."}'| Connector | Provide | How to get it |
|---|---|---|
| an address | nothing to set up | |
| Slack webhook (no buttons; use the Slack app above if you can) | an incoming-webhook URL | Slack: Apps, Incoming Webhooks, Add to Slack, pick a channel, copy the URL |
| Microsoft Teams | a webhook URL | Teams: channel Workflows, "Post to a channel when a webhook request is received", copy the URL |
| Phone | an international number | nothing to set up |
Slack, Teams and phone need the Team plan or above (included in every trial). Webhook URLs are secrets: don't commit them. Coding agents: ask the person to paste them.
What Pilot sends unprompted
- Once, on takeover: what it adopted and its first review.
- When a request is answered: by whom, and what changed. With the Slack app this is a reply under the request.
- When Pilot itself has a problem: its sandbox keeps stopping, cloud access broke, or an approval couldn't be applied.
Routine activity goes to the ledger, not your inbox.