Changelog
Every arcy.js release, newest first, with what changed and what your code must change to take it.
Every arcy.js release, newest first. When a release lists what your code must change, your coding agent can make those changes for you: run Update arcy.js from ARCY MCP, in Claude Code as /mcp__arcy__update_arcy.
0.8.9
Widget
- A typed answer counts. Typing the name of an option instead of pressing it picks it, and "2 kişi" is read as 2. Typing never approves anything.
Agent
- A long list is searched by name without being carried whole. When ARCY looks up which record a visitor means, the widget sends only each record's id and name, so a list of forty stays fits where three did.
- A Lookup offers only the records it should. An Operation can say which states a record may be in, and the widget leaves the others out before anything is sent.
Flows
- An optional value left empty is not sent. A JSON body no longer carries an empty optional input as
null; the member is left out, the way a query parameter already is.
0.8.8
Widget
- One record is drawn as labels and values. A read that answers with a single record, such as one booking, now shows its fields as a short list of labels and values. A table of two or more rows keeps one thin line under its header, in your theme's border colour.
- A typed name picks the card it names. When ARCY shows picture cards to choose from and the visitor types one of their names, such as "sörf koyuna bakan loft", that counts as pressing the card. Typing never approves anything: the Yes on an approval is still the only way to say yes.
- A question that runs out no longer blocks the chat. When a visitor leaves a card unanswered until it expires, or the connection drops while ARCY is asking, ARCY lets go of that question. Before, every step after it was refused until the page was reloaded.
- Waiting stays on the newest turn only. A turn that ended on the visitor's move keeps its Waiting mark until they answer, and the mark leaves the turn once they do.
- Dates are read in the visitor's own day. Once the visitor has granted consent, the widget sends the browser's time zone with each message, so "tomorrow" and a check-in date mean the visitor's own day.
Flows
- A missing field no longer fails a request. When an Endpoint's answer leaves out a field you declared, or sends it empty, ARCY leaves that field unset and goes on. A value of the wrong type still fails the step and names the field.
- A request reports its Endpoint's Event. A Flow's request step reports the Event its Endpoint declares under Reports Event, so a booking a Flow makes counts like one made in the chat.
0.8.7
Widget
- One setting says what ARCY may read of the page, and the widget obeys it twice. It reads every page, public pages only or never, and it lives on Settings > Consent and legal. The ten Ability switches it replaces are gone. The server decides first and the widget refuses a page read again on its own side, so one mistake on one side is not enough to read a page you said was private.
- A Procedure's Preview plays on your own Development page. Press Preview in the dashboard and your page opens with the sample's first message already in the box, for you to read and send. Your page session sends no visitor telemetry while a Preview runs, so your own walkthrough never lands in your numbers.
- A refused Preview says so and locks the chat. When a Preview cannot start, ARCY tells you why, and the bar stays read-only with a not-allowed pointer over it, so a chat that cannot work never looks like it can.
Agent
- ARCY answers from one Procedure at a time. A Procedure is a named piece of work your Product can do, written once and approved by you, and the agent now picks the one that fits what the visitor asked and follows it. Where it has no Procedure for the question, it answers from what it has read of your Product and does nothing else. Nothing in your page changes: the whole thing is chosen in the dashboard.
Flows
- A write answers in one of four Outcomes. An Endpoint that changes something now declares what its API already says: done, needs the visitor (with one link), pending (someone else decides later) or refused (with a reason it declared). ARCY draws each as its own card, so a declined payment never ticks as done and a payment that needs the visitor's own step hands them its link. This replaces the success condition of 0.8.6. An Endpoint that declares nothing is still read as done on a 2xx answer.
0.8.6
Widget
- The panel speaks the visitor's language end to end. Every word ARCY draws, its buttons' names and tooltips included, now comes in the panel's language. The watermark reads "ARCY ile çalışır" in a Turkish panel, and the calendar's month arrows and the stepper's minus and plus say what they do when pointed at or read aloud.
- Dates are written out. A visitor who picks 13 to 16 November sees "13–16 Kasım 2026" in their own bubble, never
2026-11-13/2026-11-16, and the calendar's footer reads "Giriş: 13 Kasım · Çıkış: 16 Kasım". The calendar spans the full width of the panel, and its days, arrows and the stepper's buttons grow to a finger's size on a touch screen. Your Endpoint still receives the dates as ISO. - Every whole number is a stepper. A guest count, a number of nights or a quantity is asked with minus and plus whatever its range, starting at 1, and a large number can be typed straight in. Only a value that may carry a fraction keeps the text box.
- Your page's language outranks the panel's own pick. The panel reads your page's
<html lang>every time it starts, andarcy.selectLocale()sets it. A visitor who chooses a language in the panel's settings keeps that choice across reloads, and your own language switcher releases it: when the page changes language, the panel follows the page. One language then governs the whole turn, so a card and the button beside it can no longer disagree. - A card without a photo keeps its place. In a comparison or a grid, a listing with no photo, or whose photo fails to load, gets a block of the same size with its first letter, so the rows still line up across the cards.
- ARCY can sit against an edge or in a corner. A theme now chooses where the chat opens: centred over the chat bar as before, as a full-height Side panel against the left or right edge, or as a Corner panel that rests as one round button in a bottom corner and opens above it. Pick it on Appearance, in the theme's Sizes sheet under Chat panel. Your width and height settings size all three, and under 640px wide every one of them opens the full-screen panel.
- A side panel and a corner panel stay open while ARCY works on the page. The visitor watches the clicks happen beside the transcript instead of losing the conversation. When the control ARCY needs is behind the panel and scrolling cannot bring it out, the panel folds for that one step and comes straight back.
- The corner button opens and closes the chat. Under a corner placement the button never disappears: it shows a chevron while the panel is open, closes it on the next press, and carries one dot when a reply lands with the panel shut. The widget rests as that button whatever How ARCY rests says, and visitors cannot drag it.
- A price is asked in lira, not in kuruş. When one of your Endpoints takes an amount and says so, ARCY asks for it with a plus and minus counting in whole lira, prints it with its own symbol as the visitor steps, and still sends your API the value in the unit it takes. A host setting a nightly price of ₺1.800 reads ₺1.800 while they choose it, not the 180000 the call carries.
- A typed amount is read the way it was written. Both "49,99" and "49.99" are forty nine and ninety nine, and both "1.800" and "1,800" are one thousand eight hundred, whatever language the panel is in.
- A question opens on the value you already hold. A guest count of 4 on a booking now opens its stepper at 4, not at 1, and a change to a 15 December trip opens the calendar on December, not on today's month. ARCY reads it from the record the step is bound to, and the visitor still presses Confirm, so nothing is sent unseen. A price is never opened this way, because the record and the stepper count in different units, and a text box is never prefilled.
- A calendar can open with the days already picked. When the visitor named the dates in the conversation, or the record holds them, the calendar opens on that month with the day or the stay already marked, and Confirm is live. Days outside what your Endpoint allows are ignored, and a stay that lost one of its days opens empty rather than half filled.
- The calendar and the picture cards use the full width of the panel. The row that holds them no longer stops short of the right edge.
- A figure the visitor named opens the stepper. "Iki kisilik", "for two" and "zwei Personen" open the guest count at 2, and "3 nights" opens the nights at 3, ahead of what a record holds. It is checked against your Endpoint's own limits, is never applied to an amount, and the visitor still presses Confirm.
- A choice the visitor named wears the Recommended mark. In a row of listed options, such as a plan or a payment method, the one the visitor already wrote is marked and comes first. It is never chosen for them.
- An email, a web address or a phone number already written opens in the composer. When ARCY asks for one and the visitor gave it earlier in the conversation, the box is filled and they press Enter. A second one of the same kind, a date that looks like a number, a password and anything the visitor has already started typing are never filled.
- A meter row with nothing to measure draws no bar. A figure that is not a number, or a limit of "Unlimited" or zero, shows its printed figures and no empty bar that would read as nothing used.
Agent
- An approval asks in your words, in the visitor's language. Each Endpoint now carries Visitor wording: a first-person approval question, a step label, a label and a question for each input, and the Open after button's words, in English and in every language the Product serves. A Turkish visitor reads "Kayıtlı kartınızla rezervasyonu yapayım mı?" over rows labelled İlan, Tarihler, Misafir and Kart, where they used to read the Endpoint's raw name and its English notes. An Endpoint nobody has worded yet shows ARCY's own neutral words in the visitor's language, never its name.
- An id never reaches the screen. A record on an approval is named from anything the conversation has read, or by one quiet look-up before the card draws. When it still cannot be named, the row is left out and the card says ARCY cannot show which record it is.
- A comparison is drawn whenever a read declares one. An Endpoint that reads can declare how its result shows: side-by-side cards, a grid of photos, or a list, with the fields it fills. ARCY draws it above its answer at the end of the turn, and draws nothing when the read was only a step toward a booking or another change.
- ARCY alone asks for an Endpoint's missing values. The model can no longer ask for a value an Endpoint takes in its own words, so a question is always asked once, in the visitor's language, with the right control.
- ARCY fetches the price rather than working one out. When an operation of yours answers with an amount and changes nothing, ARCY calls it itself the moment it has everything that operation needs, and hands the agent the real figure. A guest asking what three nights cost is told the total your own site would charge, including cleaning, service and tax, instead of the nights added up. ARCY does this at most once a turn, draws no step for it, and never does it with an operation that changes data.
- A quote is never guessed. The agent is told it may not add amounts up or name a figure it did not read.
- A pick is not asked twice. The listing a visitor tapped on one turn is remembered on the next, so a typed "yes" that begins the next turn goes straight to the approval card instead of asking which one again. What they name last decides, and two names ask again rather than guess.
- The date and the number a visitor already gave are not asked again. A date range, a guest count or a night count named in words, in any of the four languages, is read from the conversation and offered pre-filled, and a value the visitor wrote in words is no longer discarded as something the agent made up.
- Results are shown, not written out. When a turn reads a list and then writes it as bullet points, the agent is asked once to show it as cards, a list, a comparison or a chart, or to ask with tappable choices. A question the agent types for a value an operation takes is likewise sent back to ARCY's own card.
- Pictures are found without being asked. A grid, a list, a comparison or a choice of products shows its photos whether or not the agent named the image field, still only from the image hosts you allowed.
- A link an operation returned stays a link. A payment page, or any address your own operation answered with, is kept in the answer this turn and when the visitor asks for it again later. An address the agent invented is still removed, and a sentence whose only link was a "click here" that had to go is removed with it.
- A chart over unlike units, or a bars chart with a negative row, is refused with a reason the agent can act on, where it used to be drawn.
- A step that did not run no longer shows a tick. A request the browser skipped is drawn as not done, next to the sentence that says it did not go through.
Flows
- A step reads what a yes looks like, not only what a failure looks like. An Endpoint can now declare its success condition: the call went through, a field equals a value, or a field is one of several. A 2xx answer that says "declined" now stops the step instead of ticking it as done. A condition this build does not know is read as nothing declared, so a newer dashboard never stops a Flow that works on an older widget.
- A step that stopped on its own signal still tells ARCY what the answer said. The fields your Endpoint declares reach what ARCY says next, so a visitor sent to finish a payment still gets the link. They never set a Run variable, never fire an Event and never feed a later step.
Fixes
- An approval left unanswered says so. After five minutes the card is retired in place, its buttons gone and marked expired, and a line says nothing was done and typing carries on. A press that lands after the wait ran out is never taken as a yes.
- A finished Step card always has a title, live and when the conversation is reopened, and step rows never show an Endpoint's raw name.
- Smaller fixes to the panel. The thin lines under the header and above the watermark are gone, the composer's buttons sit equally far from its edges, and a file that is not a picture shows the start of its name with its extension under it.
- Starting a new conversation ends the turn still running in the old one. Before, the old turn kept waiting on its card, the next message reached it as a correction, and the visitor read "queued for the next step" and nothing else. The card is withdrawn first, so the step reads as declined and nothing is written.
0.8.4
Widget
- ARCY can put two to four options side by side. A visitor asking which of two places is better got two paragraphs to hold in their head. ARCY now answers with a comparison: one column per option, its picture and a link on top, the same rows under each, so the difference is read across a line rather than remembered. A grid of three or more pictures, or a comparison, widens the panel to most of the screen while it is the latest answer, and the panel goes back to its own width with the next plain answer or when it is collapsed. Your scroll position and anything typed in the box are kept. On a phone nothing widens.
- A question whose options have pictures shows them as cards. When ARCY asks a visitor to choose between listings or products that carry a photo, each choice is a pressable card with its picture, two or three to a row, and the one ARCY suggests carries a Recommended mark.
- Dates and small numbers are picked, not typed. A question asking for a date opens ARCY's own calendar in the visitor's language, with days that cannot be chosen greyed out, where it used to be a text box asking for the date written as yyyy-mm-dd. Two dates asked one after the other, a check in and a check out, are one calendar answered with two taps. A whole number in a small range, such as a guest count, is a minus and plus stepper that stays within the limits your Endpoint declares.
- The widget follows your page's language on its own. When your site's language switcher changes
<html lang>, the panel's own words, its starters and the next answer switch with it, without a reload, as long as that language is enabled for the Product. Messages already sent keep the language they were written in. A switcher that does not touch<html lang>can call the newarcy.selectLocale(code)instead.
Agent
- An approval is a plain Yes or Not now. The third choice, allowing an action for the rest of the conversation, is removed. An Endpoint you have set to run without asking still runs without asking; that was always your decision, not the visitor's.
- An approval says what it will do in words. The question used to print the Endpoint's raw name ("Shall ARCY book_with_saved_card?"). It now names the action in plain words, and a saved card reads as "Visa ending 4242" rather than as an id. A hand-over to your team asks once, says where the reply will go, and no longer prints the drafted note first.
Flows
- A finished Step card says how it ended in its own header. The separate centred line under the card ("Completed: list_trips") is gone, live and in replayed conversations, because it said again what the card already said. The outcome now sits at the right end of the card's header, as an icon and one word: completed, partly done, could not finish, or stopped. The icons are the same circle set the step rows use.
Trust and safety
- A message the safety filter is unsure about still gets an answer. An ordinary question could be flagged as an attack, Turkish ones most often, and the visitor received a fixed request to rephrase. A flagged message is now answered in a guarded turn: ARCY can read and reply, but takes no action on the page, writes nothing and starts no Flow until the next message. A message holding card, bank or password details is still not read at all, and the visitor is told so in their own language.
Fixes
- A table is never drawn as a table. A wide grid of cells does not fit a chat bubble, and ARCY has a proper surface for every kind of list. If the model writes one anyway, each row becomes its own short block with the column names as labels, so nothing in it is lost and the bubble is never left empty.
- One turn shows one Step card. When ARCY called one of your Endpoints from inside a step, a second, empty "Working on it" card opened under the first, so one request looked like two things loading. The step's own row already shows the call running, and that is now the only place it shows.
- Smaller fixes to the panel. The attach control is a paperclip and sits on the same row as the box when attachments are on. The fade at the top and bottom of a long conversation is a thin line now, drawn only when the conversation scrolls. Figtree joins the fonts a theme can choose.
0.8.3
Widget
- A card ARCY looked up can be opened. An answer drawn as cards, a set of search results or a list of orders, showed the picture and the price and then went nowhere, so a visitor who found what they wanted had to go and find it again themselves. When your operation returns the page's own address, the whole card is now a link to it and opens in the same tab, with the chat still there to come back to. Only an address on a Domain you have verified is used; any other one is left out and the card still draws.
- A visitor can attach a document, and ten images instead of three. Someone whose question was about a receipt, a contract or an export had to put the file into words, because the picker took pictures and nothing else. You decide what may be attached, with Visitors can attach images and Visitors can attach documents on Appearance, and the picker offers exactly what you ticked and nothing more. One message carries up to ten images and one document beside them; an image stays capped at 5 MB and a document at 4.5 MB. Documents start switched off, because letting people send files into your product is your decision to make rather than ours. The list is read again each time the picker opens, so a type you untick reaches a page that is already open the next time its widget starts, with no release from you. Anything outside your list is refused by the server as well, so the picker is the courteous half of that check and never the control.
- One message length, 2,000 characters, with the box saying so before a visitor runs out. The widget carried its own 10,000-character ceiling, written down in a second place and free to drift from the one the server enforces, so a long question was accepted by the box and then refused by the request. The length now arrives with everything else your Product sends the widget as it starts, which leaves one number instead of two, and it is held between bounds on the way in so a tampered answer can neither lift the ceiling past what the server takes nor shrink the box to nothing. A counter appears once a message is four fifths of the way to the limit, and a paste longer than it is cut to fit with a line that says it was cut, rather than quietly losing its tail.
Trust and safety
- A picture in an answer loads only from a host you named, and a list of records now carries one too. A picture in a card drew from any address at all, while the Appearance page said it had to come from a Domain you had verified, so the page promised a rule the product was not keeping. Settings > Image hosts is where you name the hosts a picture may come from. There is no DNS record to add for one, because letting a picture through is a smaller decision than letting a script run, and a shop's pictures usually sit on a CDN it does not own. Every Domain you had already verified is on the list from the first day, so no answer loses a picture it was drawing. A picture from any other host is left out and the card still draws its words. A list of records shows a small square beside each line as well, where a card shows a wide picture above its words, so a list of products or orders can carry thumbnails.
Fixes
- A long address is kept whole instead of being shortened. An address longer than the limit that applies to a card's words was being cut to fit it, which turns a working picture into a broken one and says nothing about it. An address is now measured against its own limit, and one past that is left out rather than cut, so a card either shows its picture or shows none.
0.8.2
Agent
- ARCY can point at a section, not only at something to press. A visitor who asks where the FAQ is, or where the pricing table sits, is asking about a part of the page rather than about a button. ARCY now settles a note onto the page's own headings and draws it there without a press button, because a heading is not something anyone can press. A control and a link still carry theirs. Only a note reaches a heading: a press and a fill never do, so nothing can act on a title.
- An Ability you switched off is refused on the page as well as on the server. The widget now reads the Abilities your Product sent it the last time it started, and refuses an act one of them forbids. The server is still the gate; this is a second refusal behind it, so one mistake on one side does not undo the setting. A flag this build has never heard of reads as on, which means no release can quieten an agent that is working, and an Ability you switch off in the dashboard reaches an already open page the next time that page's widget starts.
Flows
- The Run marker reads Completed only when every step succeeded. A run carrying a step that failed, one the visitor declined or one they stopped no longer shows the same word as a run that did all of it.
Analytics
- A run that did every step is counted as a completion. When a Flow's author wrote its own ending, the run that had done its job was reported to you as a visitor walking away, so your funnel recorded your best runs as losses. A finished run now sends the event its own Run marker shows: every step done sends
flow_completed, an ending the author put on a failure branch sendsflow_errorwith the reason why, andflow_abandonedis left for the one thing it describes, a visitor who left of their own accord. Nothing changes on the visitor's screen. What changes is that your numbers agree with what happened.
Fixes
- A name renders as itself. A name an operator typed, a value an endpoint returned and a label read off your page all land on a surface that reads markdown, and not one of them was written as markdown. A name holding
**was being set in bold, one opening#turned into a heading and a backtick opened a code span, which is ARCY reformatting somebody else's name. Every markdown character in a value from your data is now escaped, and an identifier such aschurn_risk_scoreis shown in a code span instead. Bidirectional overrides are removed rather than escaped, because there is no escaping an instruction that reorders whatever the surface draws after it. Emoji families and Arabic and Indic names are untouched: the joiners they need stay. - A line the agent wrote on its own line stays on its own line. A single newline in an answer was not treated as a line break, so a correct three-line reply ran together into one paragraph.
0.8.1
Widget
- When the only answers are buttons, the typing field closes. An approval ask shows its own Yes and Not now, and the composer underneath used to stay open: a visitor who typed "yes" there was told to pick one of the options instead. The field is now closed for as long as a card owns the answer, and its placeholder says to pick an option above. The same fix closes it for a password card and a date picker raised mid-run, which had the same gap.
Agent
- ARCY finishes a job that takes more than one step. Ask it to add the double stroller to your basket and use your coupon and it works out every action it can take on the page as it is right now, shows you that whole run on one card as numbered rows, and does all of it when you tap Yes, do it once. Until now it asked you to agree to every single press, three or four cards for one request, and more often than not it did the first thing and explained the rest in words. When an action changes the page, ARCY reads what is there now and shows you the next short run, with its own Yes, so a four-step checkout costs you two taps instead of nine. The cursor, the glow and the Cancel pill stay on your page for the whole run, so one Yes is never a point of no return.
- ARCY looks inside a closed menu before it says something is not there. Ask for a setting that sits in an account menu, a "more" button or a settings drawer, and ARCY opens it, reads what is inside and closes it again, with the cursor on the control while it looks. When it finds the control, the card says where it is, "Press Light theme in the User menu", and one Yes, do it opens the menu and presses it. It never tells your visitor your product lacks something it did not see, and it never sends them to their device or browser settings unless your own content says to. Nothing it saw is kept.
- Saying "not now" stops the whole run. Nothing half-runs: ARCY tells you what the earlier cards already did, names what it did not do, and asks what you would like instead. A run also stops where an action fails or where the page turns out not to be what it expected, and ARCY reads the page again rather than pressing something you were not shown.
Flows
- The agent says what it is doing, not what is to be done. Each row of the step card used to name the task in the infinitive, which reads as a list of things somebody still has to get round to. It now says what ARCY is doing at that moment, in the first person, in every language the panel speaks: "I'm searching the help content", "Olaylar sayfasını buluyorum". The title above the rows names the whole task, and addresses the visitor as "you" instead of by name.
- Every step mark is a standard icon. The step card drew a tick of its own invention, and three of its seven states had no mark at all, only a ring. Each state now draws the same icon set the dashboard uses: a plain ring for a step still to come, a turning ring for the one running, a pause for a step waiting on the visitor, a filled check in your brand colour for one that is done, a minus where the visitor said no, a cross where they stopped the run, and a slash where ARCY could not do it. The visitor's no and the visitor's Stop used to share one mark and now read apart.
- A finished run's line is centred, under the Flows mark. The line that says a run is over sits in the middle of the thread with the same icon the dashboard gives Flows, so it reads as a marker of something that happened rather than as a heading with a stray shape beside it.
Trust and safety
- The chat answers before anyone agrees to cookies. A visitor who refused your banner, or who has not answered it, opens the chat, asks their question and gets an answer. Nothing is written to their device while they have not agreed: the conversation is held for that browser tab and goes when they close it. Storage is what the chat asks for, never what it needs to answer, so a refused banner no longer costs a visitor the help they came for.
- The ask became an offer, and refusing is one tap. It appears when the visitor reaches for something that genuinely needs their device, which is their chat history, anything that remembers them across visits, and a step that writes an attribute about them, plus once after their first answer. It carries Accept and No thanks at the same size and weight, neither styled as the one to press, and it opens on what the visitor gets rather than on what we store. No thanks is a refusal, held six months, and the chat keeps answering.
- A visitor can withdraw where they agreed. Withdraw consent sits in the chat's own settings. It removes everything ARCY wrote to their device, resets their anonymous id and tells your banner, and their conversation carries on for the rest of the tab. The line under it says in one sentence that conversations already stored stay, and links your privacy page for having them erased.
- ARCY never asks for storage on its own again. A visitor who gets stuck used to be shown the consent ask by a flow that matched them, which asked them for something that would not solve their problem. That is gone. The one thing ARCY still raises by itself is the single offer after an answer, once per page load, and never to a visitor who said no.
- Every visitor is asked once more. What the ask covers changed, so the record of an older answer no longer matches it and the question is put again under the new wording. A visitor who accepts is remembered exactly as before.
- Consent travels one way, and our documentation says so. A grant given to ARCY covers what arcy.js stores and nothing else: your banner's answer binds ARCY, an ARCY accept never binds your banner. Two recipes that said otherwise are deleted from our consent docs page, the Google consent-mode block and the call to a consent platform's accept-all. If you had wired either one, remove it;
arcy.onConsent()is for reading a visitor's answer so your own banner can show it, never for granting anything else. Nothing else about the three calls changed: your banner keeps callingarcy.consent(true)andarcy.consent(false)exactly as before. - You can switch the whole thing off per Product. Answer before consent, on the Consent card of Configure > Legal, ships on. Off, the widget waits for your banner: no answer on record, no chat, which is the shape a security review asking for a banner-gated widget wants.
- A field that is yours stays yours. When a run reaches your card number, your password or a one-time code, that row is on the card before you agree to anything, the run stops there, and ARCY says which field is yours and what is left after it. It still never reads or types one, and it never asks for one in the chat.
Fixes
- The step counter tells the truth. A run of four says "step 2 of 4" while it works, instead of "step 3 of 3" on every card.
0.8.0
Widget
- Reloading the page no longer empties the chat. Open the chat after a refresh and the conversation you were reading is back, drawn from the same record ARCY already kept. If a run was working when the page went, it says so, and offers to pick it up where it stopped. An operation that changes your data is never picked up automatically after a reload, because nobody can know whether it went through; ARCY says that instead of repeating it.
Agent
- ARCY can see your switches and knows which way they are set. A toggle, a checkbox row or an icon button that takes its name from a label beside it, rather than from text inside it, used to be invisible to ARCY: it would read your page, find nothing it could press, and tell you so. Every component library writes controls that way, so this covered most settings rows on most pages. ARCY now reads a control's name the same way a screen reader does, and reads its state with it, so "turn off the weekly summary" acts on the switch you meant instead of pressing a switch that was already off.
- Saying yes once means once. When you agree to an operation that changes your data and it fails, ARCY no longer asks you to agree to the same thing again. One agreement covers one attempt: if that attempt does not go through, ARCY tells you what happened and what you can do about it, and it will not run the operation again on the strength of the same yes. Correcting a value and trying again is a new operation, so it asks again, which is right. Saying "not now" holds for the rest of the turn too.
- A run ends when the page does. Closing or reloading a page mid-run now ends that run on the server at once, instead of leaving it working for a browser that is not there.
What your code must change
- If this install is older than 0.8.0, earlier releases are not recorded here: check the install against the rules of the Install arcy.js prompt of the ARCY MCP and fix only what differs.