Follow these ten straightforward steps to install myiDecide AI, sign in, build your presentation and share it. There is nothing to configure — the AI runs through your myiDecide account.
The myiDecide AI is a Chrome extension that sits beside your myiDecide Builder. Answer a few questions and it writes the script, designs every slide, finds the footage, records the narration and wires up the menus — while you watch it happen in your own myiDecide Builder tab! Afterwards, just tell it if you want anything changed!
The myiDecide AI runs in Chrome's side panel next to your myiDecide Builder on a laptop or desktop — it does not run on a phone or tablet.
chrome://extensions, switch on Developer mode (top right) and click Update.
iDecide AI writes and designs through your myiDecide account: every request the Extension makes goes to myiDecide, which runs it on iDecide's own AI and counts it against your daily allowance. The only thing it needs is that you are signed in to myiDecide in this Chrome window.
The myiDecide AI works inside one presentation at a time, in the tab that is in front of you.
my.idecide.com/builder/create/123), or choose Make me a new one when the Extension asks if you already have a presentation open.
Answer the questions in the Extension, including your company, audience, offer and calls to action. When you are ready, use Skip the rest & build → or finish the final question to start the build.
While it runs, your Extension tab is covered by a soft blue wash with a short message. It is there to stop stray clicks — the myiDecide Builder underneath is being driven by the Extension, and a click or tab switch at the wrong moment can freeze it mid-slide.
Nothing is charged to you and there is no bill to watch. Instead, every myiDecide account has a daily iDecide AI allowance, and each build, each resume and each edit request uses part of it. When it runs out, builds pause until it resets — and nothing already built is lost.
| What you do | Share of the day's allowance | Notes |
|---|---|---|
| A full build | about a fifth of a day — a 58-slide build measured 18 % (October 2026) | roughly five such builds a day; a shorter presentation uses less |
| Resume after a stop | only what was left | finished slides are never redone |
| An edit request | a small fraction of a build | one slide at a time; attachments use a little more |
The share depends on the presentation's length (a 58-slide deck uses more than a 20-slide one) and on how much is attached — the panel shows the exact figure for every build it finishes. If the allowance runs out mid-build you'll see ACCT-02: wait for the reset, then Resume build from History.
Every build is listed under History in the Extension (the clock icon at the top of the panel). From there you can resume an unfinished AI build, reopen the edit chat for a finished one, edit its script and rebuild, restore the original, or download the build record — a file that shows every step the build took, which is what to send if you ever need help.
The edit chat is where a finished presentation gets changed: describe what you want in plain words — reword a headline, swap a clip, add a slide, change a button — and the Extension makes the change in your myiDecide Builder and tells you what it did. You can keep typing while it works; later messages wait their turn, and Stop halts the current change without undoing anything already applied.
The finished presentation is an ordinary myiDecide presentation in your account — nothing lives in the extension. Play it, preview it on your phone, and send it to prospects exactly as you would any other: from myiDecide's Publish step, with the viewer's name and your contact details filled in automatically from the [viewer-name-first] and [sender-…] fields the build placed on the slides.
When the build finishes, press Reload the Builder & take a look. If you want anything changed, press Ask for changes ✎ and describe it in plain words.
In that chat you can also hand it your own files: press the 📎 beside the message box to attach a picture, a video clip or a document (a brochure, a price list, a one-pager) and say where it should go. Pictures and clips are uploaded into this presentation’s own media library, so they stay with the presentation; documents are read so the wording and figures used are yours. Keep the presentation’s tab the one you can see while a change runs — the myiDecide Builder pauses when its tab is hidden, and the panel will tell you so rather than leaving you waiting.
Every message the extension can show, what it means in plain English, and what to do. The extension quotes the code (for example TAB-02) next to the message so you can jump straight to it.
| Code | What you'll see (short) | In one line |
|---|---|---|
ACCT-01 |
"You're signed out of myiDecide" · API 401 |
Your myiDecide session ended — sign in on the tab that opens; the panel carries on by itself |
ACCT-02 |
"Today's AI allowance is used up" · API 429 rate_limit_error |
Your account's daily iDecide AI allowance is spent — it comes back at the reset time in ⚙ Settings |
ACCT-03 |
"That model isn't available right now" · 404 not_found_error "model: …" · 403 permission_error |
The model iDecide AI builds with couldn't be reached through myiDecide — wait a few minutes |
ACCT-04 |
"iDecide's AI account needs topping up" · API 400 "Your credit balance is too low" |
The AI service refused iDecide's own account (its prepaid credit is spent) — not your allowance; email hi@idecide.com, then Resume |
API-01 |
"The AI request was refused" · API 400 / invalid_request_error |
The request was sent and refused; usually temporary — resume, then send the record |
API-02 |
"iDecide AI is busy right now" · 529 overloaded_error · API 502/503 |
The AI service is overloaded or briefly down — wait a minute or two |
NET-01 |
"myiDecide couldn't be reached" · "Failed to fetch" | No answer from my.idecide.com — connection, captive Wi-Fi page, firewall or VPN |
TAB-01 |
"Open your presentation in the myiDecide Builder first" · "I'm not seeing a myiDecide tab in front" | The panel can't find the myiDecide Builder tab it should work in |
TAB-02 |
"Your presentation's tab has to be the one you can see" · "the build tools never loaded … because <reason>" | Chrome is not drawing the myiDecide Builder tab (minimised, behind another window, or behind another tab) so it never finishes starting |
TAB-03 |
"builder error dialog detected" · "The myiDecide Builder crashed N times … mid-update" | The myiDecide Builder showed its Unknown Error dialog |
TAB-04 |
"slides.changeSlide did not answer in 30s" · "could not open <slide> — skipped" · "export timed out after 20s" | The tab lost focus or the computer slept during a long pass |
TAB-05 |
"This presentation is open in another tab" · 409 SESSION_MISMATCH |
The same presentation is open somewhere else and holds the lock |
TAB-06 |
"This myiDecide Builder is out of date" · "no stock media calls" | The builder page is older than the extension (or cached) — hard-reload it |
BUILD-01 |
"A build is running in your myiDecide Builder tab right now" | Edits wait until the running build finishes |
BUILD-02 |
"I couldn't read any text out of <file>" | The uploaded script or brochure has no readable text |
BUILD-06 |
"…is 140 MB — the limit for videos is 96 MB" · "Six files at a time is the limit" · "could not be uploaded into the presentation" | A file attached with the paperclip is over a limit, or the presentation tab wasn't reachable to upload it |
BUILD-03 |
"wire: unknown target" | A button pointed at a slide that doesn't exist — repaired automatically since 1.1.0 |
BUILD-04 |
"(NO VOICEOVER)" is spoken aloud | A silent-slide marker was narrated — fixed in 1.1.0; older decks can be cleared |
BUILD-05 |
"iconify unreachable" · "display font unresolved" | An icon or font service couldn't be reached; built-in fallbacks were used |
BUILD-07 |
"The AI's plan came back garbled" · non-JSON reply (N chars…) |
The AI's plan wasn't in the exact format the extension reads — resume and it almost always comes back clean |
BUILD-08 |
"Imagery on <slide> was blocked (…) and could not be replaced automatically" | A stock clip or photo the brand must never show was refused and no safe replacement was found in time — ask in the chat to replace it |
PANEL-01 |
The side panel was closed while a build was running | Reopen it — History → Resume carries on where it stopped |
GEN-01 |
"Something went wrong" | A problem with no specific explanation yet — try again, then send the build record |
HELP-01 |
You need to send something to support | Where the build record is and what to send to hi@idecide.com |
Since 2.3.0 the extension sends every AI request to myiDecide (the backend at my.idecide.com), which runs it on iDecide's own account and counts it against a daily iDecide AI allowance for your myiDecide user. You never paste a key: the only thing the extension needs is that you are signed in to myiDecide in Chrome. ⚙ Settings shows who you are signed in as and how much of today's allowance is used; the slim bar at the bottom of the panel shows the same figure while you work.
What you'll see
API 401: not signed in to myiDecide.What it means
myiDecide no longer has a signed-in session for this Chrome profile. The session expired, you signed out in another tab, or you signed in to myiDecide in a different browser or profile. Nothing already built is lost — the presentation lives in your myiDecide account, and the build record is kept in the panel.
What to do
If it keeps happening
HELP-01.What you'll see
API 429: … rate_limit_error … and the build stopping
rather than retrying.What it means
Every myiDecide user has a daily iDecide AI allowance, and today's is spent. It is a cap on how much AI work your account can ask for in a day — a very long presentation, several builds in a row, or a lot of edit requests will reach it. The panel stops the build at once instead of retrying until the reset, so no allowance is wasted on refused calls. Nothing already built is lost.
What to do
If it keeps happening
HELP-01.What you'll see
API 404: … not_found_error … model: … or
API 403: … permission_error ….What it means
myiDecide accepted the request but the AI model it builds with could not be reached — the model is being updated on the service's side, or myiDecide's own configuration is mid-change. That is on iDecide's side, not yours.
What to do
What you'll see
API 400: … invalid_request_error … credit balance is too low … (the card itself shows no technical detail for this one — the
explanation is complete, and the raw wording is the AI service's, aimed at
iDecide's billing, not at you).What it means
myiDecide forwarded your request, and the AI service refused it because
iDecide's own account — the one every build runs on — has run out of
prepaid credit. This is not your daily allowance (that is ACCT-02) and not
anything you did; nobody's build goes through until the account is topped
up. Nothing already built is lost.
What to do
What you'll see
API 400: … invalid_request_error ….What it means
The request reached myiDecide and was sent on, but was refused — most often a request the model could not accept as sent (a very large attachment, say) or a temporary fault on the service's side.
What to do
HELP-01.What you'll see
API 529: … overloaded_error …, API 502 or API 503.What it means
The AI service behind myiDecide is overloaded or briefly unavailable. The panel retries short outages by itself; this card means they lasted longer than it was willing to wait.
What to do
What you'll see
Failed to fetch, NetworkError, ERR_INTERNET_DISCONNECTED,
ERR_NAME_NOT_RESOLVED.What it means
The request to my.idecide.com never got an answer. Usually a dropped connection, a captive Wi-Fi login page that has not been clicked through yet, or a firewall or VPN that blocks the address.
What to do
What you'll see
What it means
The panel reads whichever tab is active when you confirm, and it needs
that tab to be the myiDecide Builder — the address looks like
my.idecide.com/builder/create/<number>. The dashboard, the presentation
list or the player don't count, and neither does a tab in another window.
What to do
If it keeps happening
What you'll see
What it means
Chrome stops drawing a tab that nobody is looking at, and the myiDecide Builder does not finish starting while it isn't being drawn — minimised window, window behind another app, or another tab in front of it in the same window all count. The panel brings the tab forward itself first; when Chrome still isn't drawing it, the panel stops after a few seconds instead of leaving you watching a spinner for a minute and a half, and it names the reason it found.
Nothing in your presentation is changed by this. The failure happens before any edit is written, so the deck is exactly as it was. Since 2.1.2 the panel also prints what it was about to do, so you can see the change is only waiting.
Since 2.1.2 the panel no longer reloads the tab when the build tools are already
live in the page — the myiDecide platform sometimes rewrites its own address and
drops the aiagent= switch while the tools are still running, and reloading on
that was costing a wait for nothing.
What to do
If it keeps happening
TAB-01, not
this one.What you'll see
What it means
The myiDecide Builder itself crashed. A single crash is normal on a long build — the panel notices, reloads the page and repeats the step it was on, so you don't have to do anything. Several crashes in a row almost always mean the platform is being updated underneath you (the page's files changed while the tab was open); building through that fills the deck with empty slides, so the panel stops on purpose and keeps everything it had.
What to do
If it keeps happening
HELP-01).What you'll see
In the build log, one or more of:
STALLED: slides.changeSlide did not answer in 30sbuild: could not open "<slide>" — skipped (its wiring and timing are skipped too)wire: could not open "<slide>" — its buttons are unwiredexport timed out after 20sinspect: could not open — "<slide>" … (during edits)What it means
The myiDecide Builder stopped answering for a while. The usual cause is that its tab lost focus: the myiDecide Builder only renders — and only moves between slides — while its tab is visible, so switching to another tab, minimising Chrome, locking the screen or the computer going to sleep freezes it mid-step. The panel waits a fixed time, marks the slide as skipped and carries on, so one stall can cost a slide its design, its wiring or its thumbnail.
What to do
skipped lines. Each named
slide can be redone from the finished screen: Ask for changes →
"rebuild <slide name>". The wiring pass on a rebuilt slide runs again
automatically.If it keeps happening
TAB-02.What you'll see
409 (sometimes with
SESSION_MISMATCH in the text), or repeated 400s on every slide.What it means
myiDecide lets one tab at a time write to a presentation. Every myiDecide Builder tab gets its own session ticket, and the newest tab holds the lock. If the same presentation is open in a second tab, a second window, another browser or another device — or you duplicated the tab — the myiDecide Builder's tab is now the stale one and the platform rejects its saves.
What to do
If it keeps happening
What you'll see
this myiDecide Builder has no stock media calls.What it means
The extension finds photos and video through the myiDecide Builder's stock media tools (searchStockImages, importStockVideoBatch and the rest). The page in this tab doesn't have them: it's an older version of the site, or the browser is still showing a cached copy of one. The extension no longer has a way to source media without them, so it stops instead of building a deck with no footage.
What to do
If it keeps happening
What you'll see
"A build is running in your myiDecide Builder tab right now — I can make changes as soon as it finishes. Your message is safe to resend then."
What it means
You asked for a change while the build (or a rebuild started by an earlier change) was still working in the tab. Only one thing can drive the myiDecide Builder at a time, so the panel parks the request rather than interrupting the build.
What to do
If it keeps happening
What you'll see
"Before I write anything — I couldn't read any text out of "<file name>", and building without it would mean inventing a script instead of using yours. Upload a different export (.docx from Word or Google Docs, or plain .txt/.csv both work), or hit Skip to build from your answers and website only."
What it means
The script, brochure or deck you attached opened, but there was no text inside it to read — typically a scanned PDF (pictures of pages), a PowerPoint whose text is baked into images, an empty file, or a format the panel can't unpack.
What to do
If it keeps happening
What you'll see
wire: unknown target "<slide name>" on <slide>.What it means
A button was told to go to a slide that isn't in the deck. Before 1.1.0 this happened when the script left a slide's name blank (the answer slides of a question, most often), so the slide it pointed at was never created.
Since 1.1.0 this is repaired automatically: blank slide names are filled from the outline, slides that buttons point at are kept, and a button whose target can't be found is re-pointed at the sensible fallback (the next slide after a question's answers, or the return menu).
What to do
If it keeps happening
What you'll see
A slide that should be silent narrates the words "no voiceover", or the log
shows a narration of two words being restored "from the script (2 words)",
or audio missing after generation on a slide that was meant to be silent.
What it means
Script writers mark a silent beat with a placeholder such as (NO VOICEOVER),
(no narration), [silent], (none), n/a or —. Older versions treated
those words as the narration and sent them to the voice service. Fixed in
1.1.0: every one of those markers now means "no narration", everywhere.
What to do
If it keeps happening
What you'll see
In the build log:
iconify unreachable — using the built-in icon setdisplay font unresolved (<reason>) — the engine default will be used, or
the same for body fontWhat it means
Icons come from an online icon library (Iconify) and fonts are looked up in the myiDecide Builder's font catalogue. If the icon service can't be reached — a firewall, a captive Wi-Fi login page, or the service being down — the build uses the icon set bundled with the extension instead. If a font the brand asked for isn't in the catalogue, the myiDecide Builder's default font is used. The build completes either way; the slides just use the fallback.
What to do
api.iconify.design is allowed, or run the build on another network.If it keeps happening
What you'll see
What it means
The 📎 paperclip beside the message box (2.1.2 and later) attaches your own files to a change request. Pictures and video are uploaded into the presentation's own media library — the myiDecide platform stores them, the extension stores nothing — and the assistant then places them by name. Documents (.docx, .pptx, .pdf, .txt, .csv, .md) are read and handed over as text, so their real copy and figures can be used.
Because each message carries the file to the presentation in one go, there are
limits: 12 MB per picture, 96 MB per video, 24 MB per document, six files per
message. A file over its limit is refused before anything is sent. A file
that is within its limit but still won't go up almost always means the
presentation's tab wasn't reachable at that moment (see TAB-02) — the upload
travels through that tab.
What to do
If it keeps happening
BUILD-02, not this one.What you'll see
non-JSON reply (19613 chars; head: "{\"theme\":….What it means
The build asks the AI for each stage's plan in a strict format (JSON) that the extension then reads. This time part of the reply wasn't in that format — a single wrong character is enough — so none of it could be used.
The extension already handles most of these on its own. It mends the slips that
have only one possible meaning (a number written 06 instead of 6, a stray
comment, a trailing comma, a line break inside a sentence, an unescaped quote
mark), and if that isn't enough it asks the AI once more, telling it exactly
what was wrong and where. You only see this code when a reply got past both.
What to do
If it keeps happening
What you'll see
ERROR imagery: "<slide>" still carries pixabay <id> tagged "<word>" — replace it.What it means
Stock footage and photos come from a public library, and a search for an
ordinary subject can bring back a clip whose own keywords say it shows
something a brand must never show — a political party's flag, a protest, a
weapon, a place of worship, a graveyard, adult or drug content, horror. Since
2.3.1 the extension refuses such a clip at every step: the search drops it,
nothing places it, the review re-sources a slide the moment it is seen, the
finished deck is checked once more, and a presentation opened later for edits
is checked again. This code appears only when a slide was refused its clip
and the replacement searches could not find a safe one in time (usually the
stock service's minute was spent — see the build log for REFUSED).
What to do
If it keeps happening
What you'll see
The panel disappears (Chrome closed it, you clicked its ✕, or Chrome was restarted). When you reopen it, the build is not visibly running.
What it means
The build runs inside the side panel, so closing the panel pauses it. Nothing is lost: every finished slide is saved in your presentation, and the run's progress is saved in Chrome on your computer.
What to do
TAB-01 if it can't) and
continues from the last finished slide.If it keeps happening
What you'll see
What it means
This is the catch-all: the extension stopped on something it has no specific explanation for yet. Every failure we have seen and understood has its own code on this page — GEN-01 means this one is new to us.
What to do
If it keeps happening
HELP-01 for exactly what to send. A GEN-01 that
repeats is how new codes get added to this page.Where the build record is
Open 🕘 History in the panel. Every run that was saved has a ⬇ button
(Download record); it saves a file named
build-record-<brand>-<date>.json to your Downloads folder. It contains the
questionnaire answers, the script, every step of the build log, every edit
request and reply, and the timings — everything needed to see what happened.
It does not contain your myiDecide password or any sign-in cookie.
What to send
Email hi@idecide.com with:
TAB-04),
or the exact message if it isn't listed.my.idecide.com/builder/create/<number>).Before you send
iDecide is the company. myiDecide is its do-it-yourself platform, and this extension builds presentations on it — myiDecide presentations. iDecide presentations are a separate service: presentations the iDecide team builds for clients by hand, outside the platform.
No. Since version 2.3.0 the AI runs through your myiDecide account: the extension sends each request to myiDecide, which runs it on iDecide's own AI and counts it against your daily allowance. There is nothing to sign up for and nothing to paste. (Earlier versions asked for an API key — if you still have one saved, it is no longer used and is removed the next time the panel opens.)
Your answers, your uploads and the presentation go from your browser to myiDecide — your own account — which runs the AI step and stores the presentation. The extension itself stores nothing of yours beyond the build record in your Chrome profile. See the extension's privacy section.
Every myiDecide user has a daily iDecide AI allowance — a cap on how much AI work the account can ask for in a day. ⚙ Settings shows today's usage and the reset time. When it runs out mid-build the panel stops at once (ACCT-02), keeps everything already built, and Resume build in History finishes the job after the reset. If your work regularly needs more, email hi@idecide.com.
Yes for changes: open it in the myiDecide Builder, switch the Extension panel to Edit and ask. It can change what is on existing slides (wording, colours, imagery, buttons, narration). It won't redraw a slide it didn't design — it says so and offers to change the individual elements instead.
Yes. History → Edit script opens the full script; save it and the next build uses your version. Leave a slide's narration cell empty to make it silent — never type a marker like "(no voiceover)".
The panel can only see the sign-in of the Chrome profile it is installed in. Sign in to my.idecide.com in that same profile (not another profile, not an incognito window); the panel notices by itself the moment the login page moves on. An extension that clears cookies for my.idecide.com will sign you out again — allow the site. Full steps under ACCT-01.
Start with the troubleshooting section. If that doesn't cover it, download the build record from History (the ⬇ button) and email it with the code you saw to hi@idecide.com. Never email your myiDecide password.