IDA can now plan and implement changes across your whole org
Describe what you need in chat and IDA surveys every workspace before asking a single clarifying question, then proposes a plan spanning however many workspaces the change actually touches — one confirm dispatches all of them.
Until now, asking IDA to implement something always meant picking a workspace first. Fine when you already know exactly where a change belongs — much less fine when the honest answer is "probably three repos, but let me check." You'd end up doing that legwork yourself: hunting down which workspaces touch the resource in question, then opening the same conversation three separate times.
What's new
Open a chat with IDA and describe what you need instead of where it goes. Before asking anything back, IDA:
- Surveys your org. It lists the workspaces and repos you have, and checks which ones already manage the kind of resource you're describing — so its questions are grounded in your actual infrastructure, not a guess.
- Asks clarifying questions. Only what it still needs to know after the survey — scope, environment, specifics — not questions the survey already answered.
- Proposes a plan, not a single request. Once it has enough to go on, IDA lays out exactly which workspaces it thinks the change touches, with the rationale and the specific instructions for each one.
You get an editable proposal card right in the chat: adjust the wording per workspace, drop a target that shouldn't be included, then confirm. That one confirmation dispatches a run to every workspace in the plan, and you watch each one's status update live as it progresses — no re-opening the conversation per workspace to check in.
The same flow works from Slack: mention IDA, describe the change, and it walks the org, asks what it needs to, and posts the same confirm-to-dispatch card in the thread.
Why it matters
- You stop doing the discovery work. Figuring out which workspaces a change touches was always on you before IDA could even start. Now it's the first thing IDA does.
- One conversation, one confirmation. Not three separate requests with three separate contexts to keep straight.
- Suggestions grounded in your infrastructure. Because IDA surveys first, the workspaces it proposes are ones that plausibly need the change — not a blind guess at your repo layout.
Nothing runs until you say so
The survey step is read-only, and the proposal is just that — a proposal. Nothing is dispatched until you explicitly confirm it, and you can edit or remove any target beforehand. If a workspace in the plan already has a run in progress or an open PR waiting to merge, IDA skips it rather than piling on — that workspace is retried automatically once it's clear, and the rest of the plan dispatches normally.
How to use it
Open IDA from your organization's navigation and start a chat, or mention IDA in Slack. If your request plausibly touches more than one workspace, IDA takes it from there.