<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title type="text">Obeya demos</title>
<subtitle type="text">Videos and analyses of changes, the newest first.</subtitle>
<link rel="self" type="application/atom+xml" href="https://demos.obeya.si/feed.xml"/>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/"/>
<id>https://demos.obeya.si/</id>
<updated>2026-10-19T19:53:42.049Z</updated>
<author><name>Obeya demos</name></author>
<generator uri="https://obeya.si">Obeya</generator>
<entry xml:lang="en">
<title type="text">Question cards wait for a background job before they answer</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/question-cards-end-a-look-up-while-its-b-05f98d/"/>
<id>https://demos.obeya.si/question-cards-end-a-look-up-while-its-b-05f98d/</id>
<published>2026-10-19T19:53:42.049Z</published>
<updated>2026-10-19T19:53:42.049Z</updated>
<summary type="text">When you ask Obeya something that needs a slow job, like a download or a script that runs for a minute, the agent answering it can now run that job in the background and wait for it.</summary>
<content type="html">&lt;p&gt;When you ask Obeya something that needs a slow job, like a download or a script that runs for a minute, the agent answering it can now run that job in the background and wait for it. Before, the card took the agent's &amp;quot;still running, I'll get back to you&amp;quot; as its answer, and the result never came. Now the card shows the agent reading until the job is done, and then gives the real answer. This holds for Question cards, Obeya's side sheet and answers on a card alike.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Demo sites point back to Obeya</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/demo-sites-point-back-to-obeya-ffe710/"/>
<id>https://demos.obeya.si/demo-sites-point-back-to-obeya-ffe710/</id>
<published>2026-10-19T19:22:24.186Z</published>
<updated>2026-10-19T19:22:24.186Z</updated>
<summary type="text">Every demo page Obeya publishes, and the overview of each demo site, now ends in a small line, “Recorded with Obeya”, in the page’s language, with a link to obeya.si.</summary>
<content type="html">&lt;p&gt;Every demo page Obeya publishes, and the overview of each demo site, now ends in a small line, “Recorded with Obeya”, in the page’s language, with a link to obeya.si. Anyone who likes a demo can see where it came from. Each demo site also has an Atom feed, linked from its overview, so colleagues can follow new demos in a feed reader. Pages shared earlier get the new line when they are shared again from the Koordinator’s sheet.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Obeya's GitHub page, ready for first-time visitors</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/github-page-that-gets-found-7de95d/"/>
<id>https://demos.obeya.si/github-page-that-gets-found-7de95d/</id>
<published>2026-10-19T19:03:09.081Z</published>
<updated>2026-10-19T19:03:09.081Z</updated>
<summary type="text">The GitHub repository now links to obeya.si and carries the topics people search for, such as claude-code, ai-agents and coding-agents, so it turns up on those topic pages.</summary>
<content type="html">&lt;p&gt;The GitHub repository now links to obeya.si and carries the topics people search for, such as claude-code, ai-agents and coding-agents, so it turns up on those topic pages. Near the top, the README plays a short loop of the canvas at work, linked to the full film. A new social preview, with the wordmark and the canvas, is what a shared link to the repository shows.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Ideas wait for their agent's background jobs</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/idea-shows-your-turn-while-its-explorati-44816a/"/>
<id>https://demos.obeya.si/idea-shows-your-turn-while-its-explorati-44816a/</id>
<published>2026-10-19T19:02:41.454Z</published>
<updated>2026-10-19T19:02:41.454Z</updated>
<summary type="text">An idea's agent can start a slow job in the background, such as downloading data it needs for the discussion.</summary>
<content type="html">&lt;p&gt;An idea's agent can start a slow job in the background, such as downloading data it needs for the discussion. Until now the idea showed &amp;quot;your turn&amp;quot; as soon as the agent paused to wait for that job, and the job was stopped, so the promised result never came. Now the idea shows the agent at work until the job is done and the agent has reported back. Only then is it your turn.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Plan: making Obeya better known</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/make-obeya-better-known-28495d/"/>
<id>https://demos.obeya.si/make-obeya-better-known-28495d/</id>
<published>2026-10-19T18:57:58.955Z</published>
<updated>2026-10-19T18:57:58.955Z</updated>
<summary type="text">The plan for bringing Obeya to more Claude Code users and teams has three parts.</summary>
<content type="html">&lt;p&gt;The plan for bringing Obeya to more Claude Code users and teams has three parts. First, every demo site Obeya generates gets a small &amp;quot;Recorded with Obeya&amp;quot; credit line and a feed people can follow. Second, a weekly LinkedIn post is drafted from that week's demos. Third, a launch kit: an essay on obeya.si plus ready-to-post texts for Hacker News, Reddit, LinkedIn and the awesome-claude-code list.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Agents close the GitHub issues they fix</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/add-to-claude-md-375e47/"/>
<id>https://demos.obeya.si/add-to-claude-md-375e47/</id>
<published>2026-10-19T16:40:27.145Z</published>
<updated>2026-10-19T16:40:27.145Z</updated>
<summary type="text">When an agent's task comes from a GitHub issue, the agent now closes that issue once the fix is on main.</summary>
<content type="html">&lt;p&gt;When an agent's task comes from a GitHub issue, the agent now closes that issue once the fix is on main. Its closing comment links the demo video and the commit, so whoever filed the issue can see what changed without having to ask.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Plan docs from a folder outside the repository</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/handle-the-first-github-issue-c954a4/"/>
<id>https://demos.obeya.si/handle-the-first-github-issue-c954a4/</id>
<published>2026-10-19T14:38:12.921Z</published>
<updated>2026-10-19T14:38:12.921Z</updated>
<summary type="text">Some teams keep their plans out of the repository, for example in a gitignored docs/plan folder.</summary>
<content type="html">&lt;p&gt;Some teams keep their plans out of the repository, for example in a gitignored docs/plan folder. Obeya used to read plan docs only from what is committed on the main branch, so such plans never showed up as projects. The plan folder setting now also takes a full path on your machine: Obeya reads the plans there, and agents tick off their workstreams right in those files.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Obeya's feature demos are public on demos.obeya.si</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/share-the-30-re-voiced-past-demos-on-dem-647b7b/"/>
<id>https://demos.obeya.si/share-the-30-re-voiced-past-demos-on-dem-647b7b/</id>
<published>2026-10-19T13:49:01.314Z</published>
<updated>2026-10-19T13:49:01.314Z</updated>
<summary type="text">Obeya's recent feature demos are now public at demos.obeya.si, narrated in English: 31 short videos, newest first, each on a page of its own with chapters and a description of what changed.</summary>
<content type="html">&lt;p&gt;Obeya's recent feature demos are now public at demos.obeya.si, narrated in English: 31 short videos, newest first, each on a page of its own with chapters and a description of what changed. From now on, every demo of an approved change goes on the site by itself.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Phone: a card's question shows up as soon as you open it</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-task-with-an-open-question-op-f9ab0d/"/>
<id>https://demos.obeya.si/phone-view-task-with-an-open-question-op-f9ab0d/</id>
<published>2026-10-19T11:31:56.532Z</published>
<updated>2026-10-19T11:31:56.532Z</updated>
<summary type="text">When an agent asks something without offering answer options, its card on the phone used to open on its page: it said a question was waiting, but the question itself was behind the conversation button.</summary>
<content type="html">&lt;p&gt;When an agent asks something without offering answer options, its card on the phone used to open on its page: it said a question was waiting, but the question itself was behind the conversation button. Now such a card opens with its conversation up, the question in view and the answer field ready below it, just like a question with answer options.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Demos go public when you approve the work</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/public-demo-site-with-publishing-on-appr-50754d/"/>
<id>https://demos.obeya.si/public-demo-site-with-publishing-on-appr-50754d/</id>
<published>2026-10-19T11:00:14.933Z</published>
<updated>2026-10-19T11:00:14.933Z</updated>
<summary type="text">Obeya can now put a task's demo on a public demo site by itself as soon as you approve the task, so you no longer have to click Share separately.</summary>
<content type="html">&lt;p&gt;Obeya can now put a task's demo on a public demo site by itself as soon as you approve the task, so you no longer have to click Share separately. A new demo can replace the task's earlier page, or it can be added next to it when the new one only adds to the earlier demo. If the upload fails, the work still lands and you can share again later. When work goes straight onto main, the commit message links to the demo page, so anyone reading the history can watch the change. Obeya's own demos will be collected at demos.obeya.si, with links from the README and obeya.si, so newcomers can see every feature in action.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Obeya's replies wait as unread while the sidebar is closed</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/obeya-sidebar-an-answer-that-arrived-whi-c4329f/"/>
<id>https://demos.obeya.si/obeya-sidebar-an-answer-that-arrived-whi-c4329f/</id>
<published>2026-10-19T10:48:21.751Z</published>
<updated>2026-10-19T10:48:21.751Z</updated>
<summary type="text">Obeya sometimes answers a question straight away, without running any action or looking anything up.</summary>
<content type="html">&lt;p&gt;Obeya sometimes answers a question straight away, without running any action or looking anything up. If the sidebar was closed or you had moved to another canvas when that kind of reply arrived, it never showed as unread: Obeya's button had no count and the message had no orange edge, so a long answer could easily go unnoticed. Now these replies wait the same way looked-up answers already did. Obeya's button counts them in orange, they count toward &amp;quot;brauchen dich&amp;quot;, and the message keeps its orange edge until you close the sidebar again. Short spoken answers you ask for with the sidebar closed also wait now, while a reply that arrives with the sidebar open counts as read right away and confirmations of actions never wait.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">A task only says “Agent answered” when the agent really did</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/task-shows-agent-answered-waiting-for-yo-990f5a/"/>
<id>https://demos.obeya.si/task-shows-agent-answered-waiting-for-yo-990f5a/</id>
<published>2026-10-19T10:37:47.431Z</published>
<updated>2026-10-19T10:37:47.431Z</updated>
<summary type="text">A task used to show “Agent answered, waiting for you” even when the agent never replied to your latest message.</summary>
<content type="html">&lt;p&gt;A task used to show “Agent answered, waiting for you” even when the agent never replied to your latest message. That happened because an earlier answer stayed marked after you wrote again, and because a turn that broke off with an error still counted as an answer. Now each new message clears the earlier answer, and only something actually meant for you counts as a reply. If the agent stops without replying, the task goes back to its previous state, and the conversation says the agent stopped without answering and will carry on once you write again. That way you no longer wait on a reply that isn't coming.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Demo language per repository</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/narration-language-per-repository-dc6270/"/>
<id>https://demos.obeya.si/narration-language-per-repository-dc6270/</id>
<published>2026-10-19T10:36:09.124Z</published>
<updated>2026-10-19T10:36:09.124Z</updated>
<summary type="text">Each repository can now set the language of its demos in its own settings.</summary>
<content type="html">&lt;p&gt;Each repository can now set the language of its demos in its own settings. That language applies to the narration, chapters, report, shared pages and the site overview, and it takes precedence over the language in the machine's demo settings. Previously the demo language was set per machine, so every project was narrated in the same language. Now Obeya's own demos come out in English while another project's demos can stay in German. The demo settings also hold a voice sample for each language, so a demo in either language is narrated in the owner's own voice.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Opening the sidebar puts the cursor in the text field</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/obeya-sidebar-opened-with-c-or-the-chat-9dae17/"/>
<id>https://demos.obeya.si/obeya-sidebar-opened-with-c-or-the-chat-9dae17/</id>
<published>2026-10-19T08:39:51.146Z</published>
<updated>2026-10-19T08:39:51.146Z</updated>
<summary type="text">When you open Obeya's sidebar with the C key or the chat icon, the cursor now goes straight into the text field, so you can start typing right away.</summary>
<content type="html">&lt;p&gt;When you open Obeya's sidebar with the C key or the chat icon, the cursor now goes straight into the text field, so you can start typing right away. Before, you had to click into the field first. Opening the sidebar with Tab, while stepping through what needs your attention, leaves the cursor outside the field, so the next Tab still takes you to the next item.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Feedback sent on another canvas now gets its own draft</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/coordinator-s-wish-draft-lost-when-a-fee-f3896b/"/>
<id>https://demos.obeya.si/coordinator-s-wish-draft-lost-when-a-fee-f3896b/</id>
<published>2026-10-19T07:46:41.877Z</published>
<updated>2026-10-19T07:46:41.877Z</updated>
<summary type="text">When you send feedback about Obeya from another canvas, Obeya turns it into a draft wish.</summary>
<content type="html">&lt;p&gt;When you send feedback about Obeya from another canvas, Obeya turns it into a draft wish. Until now, if an older feedback draft was still open, the dialog showed that old draft unchanged. The new wish only appeared in one easy-to-miss line below it, so it looked as if your feedback had been lost. Now an old draft that has only a title is replaced straight away, and the new draft is written from your feedback. An old draft with text or screenshots is kept, but the top of the dialog shows the feedback the new draft will be written from, with a button to discard the old draft, and opening the old one on GitHub no longer drops the waiting wish.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Opening the archive with A leaves its search field empty</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/archive-opened-with-a-the-typed-a-lands-af8fa6/"/>
<id>https://demos.obeya.si/archive-opened-with-a-the-typed-a-lands-af8fa6/</id>
<published>2026-10-19T07:18:18.950Z</published>
<updated>2026-10-19T07:18:18.950Z</updated>
<summary type="text">When you press A to open the archive, its search field is now empty and has the cursor, so you can start typing a search straight away.</summary>
<content type="html">&lt;p&gt;When you press A to open the archive, its search field is now empty and has the cursor, so you can start typing a search straight away. Before, the A you pressed sometimes ended up in the search field too. The list then showed only archived cards containing an &amp;quot;a&amp;quot;, and you had to delete the letter before you could search. The N and C shortcuts now keep their letter out of other fields in the same way.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Headless test browsers no longer speak out loud</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/silence-web-speech-in-headless-chrome-fo-bf61b2/"/>
<id>https://demos.obeya.si/silence-web-speech-in-headless-chrome-fo-bf61b2/</id>
<published>2026-10-19T05:49:56.627Z</published>
<updated>2026-10-19T05:49:56.627Z</updated>
<summary type="text">Agents test pages in a headless browser, and demo videos are recorded in one too.</summary>
<content type="html">&lt;p&gt;Agents test pages in a headless browser, and demo videos are recorded in one too. Until now, a page that read text aloud with the browser's speech feature spoke through the computer's system voice, even though browser sound was muted. During an agent's tests that could mean a voice saying a word every half minute. Both browsers now replace the page's speech with a silent one, so nothing reaches the speakers. Pages still behave as if the text had been spoken: each sentence takes about as long as saying it would, and stopping or pausing works as usual, so pages that wait for speech to finish keep running.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Phone: comments go out when you close a card from another canvas</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-a-pending-comment-isn-t-sent-4887d8/"/>
<id>https://demos.obeya.si/phone-view-a-pending-comment-isn-t-sent-4887d8/</id>
<published>2026-10-18T18:51:31.911Z</published>
<updated>2026-10-18T18:51:31.911Z</updated>
<summary type="text">On the phone, a comment left on a card used to stay unsent after you closed the card if that card was on a different canvas than the one you were talking to Obeya about.</summary>
<content type="html">&lt;p&gt;On the phone, a comment left on a card used to stay unsent after you closed the card if that card was on a different canvas than the one you were talking to Obeya about. The comment only went out about ten minutes later, or after you opened and closed the card again. Now the card's agent gets the comment as soon as you close the card, whichever canvas the card is on. Cards on the same canvas as the conversation already worked this way and are unaffected.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Split off the settled part of an idea as a task</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/idea-agents-recommend-steps-obeya-doesn-8105da/"/>
<id>https://demos.obeya.si/idea-agents-recommend-steps-obeya-doesn-8105da/</id>
<published>2026-10-18T18:39:19.895Z</published>
<updated>2026-10-18T18:39:19.895Z</updated>
<summary type="text">When part of an idea is settled and part is still open, the idea's agent can now suggest splitting off the settled part.</summary>
<content type="html">&lt;p&gt;When part of an idea is settled and part is still open, the idea's agent can now suggest splitting off the settled part. A new button, &amp;quot;Split off a task&amp;quot;, then turns that part into a running task, and the idea stays open with its planned prototypes for the rest. Before, the agent could recommend building while prototypes were still pending. Building then ended the whole idea and silently dropped the prototypes, and the only way to keep them was to plan a full project. Now the owner can start building right away and keep exploring what's still open.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Agents can carry out what a card's task asks of Obeya</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/an-agent-can-t-pass-on-to-obeya-what-the-01654c/"/>
<id>https://demos.obeya.si/an-agent-can-t-pass-on-to-obeya-what-the-01654c/</id>
<published>2026-10-18T18:26:54.953Z</published>
<updated>2026-10-18T18:26:54.953Z</updated>
<summary type="text">When a card's task asked Obeya itself for something, like creating a canvas for a new repository, the card's agent used to be turned down.</summary>
<content type="html">&lt;p&gt;When a card's task asked Obeya itself for something, like creating a canvas for a new repository, the card's agent used to be turned down. It then had to ask you to say the same thing again on the card. Now the task text counts as your words when you wrote or dictated the card, or when you accepted an agent's proposal for it. The agent can pass the request on, and Obeya carries it out right away. A proposal you haven't accepted yet still can't make requests of Obeya, so agents can't use one to give themselves orders.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Obeya hands machine work to an agent instead of refusing</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/obeya-s-coordinator-refuses-work-an-agen-16bfc8/"/>
<id>https://demos.obeya.si/obeya-s-coordinator-refuses-work-an-agen-16bfc8/</id>
<published>2026-10-18T09:13:02.338Z</published>
<updated>2026-10-18T09:13:02.338Z</updated>
<summary type="text">Ask Obeya's main chat for something outside your repositories, like creating a new repository or installing a tool, and it now makes a task for it, and that task's agent does the work.</summary>
<content type="html">&lt;p&gt;Ask Obeya's main chat for something outside your repositories, like creating a new repository or installing a tool, and it now makes a task for it, and that task's agent does the work. Before, it said it couldn't, told you to run the git commands yourself and offered to report the request as a wish. That was the wrong answer, because a task's agent has a shell on the machine and can do this kind of work right away once you allow it. One gap is still open: when you ask for a repository plus a matching canvas, Obeya doesn't yet add the canvas by itself once the repository exists.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Phone: the keyboard stays open when you tap a misspelled word</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-tapping-a-misspelled-word-in-afcdfd/"/>
<id>https://demos.obeya.si/phone-view-tapping-a-misspelled-word-in-afcdfd/</id>
<published>2026-10-18T09:11:59.816Z</published>
<updated>2026-10-18T09:11:59.816Z</updated>
<summary type="text">On the phone, tapping a misspelled word in the chat input used to open the keyboard and close it again right away, leaving only Chrome's spelling suggestions.</summary>
<content type="html">&lt;p&gt;On the phone, tapping a misspelled word in the chat input used to open the keyboard and close it again right away, leaving only Chrome's spelling suggestions. Now the first tap puts the cursor where you tapped and opens the keyboard. A second tap on the underlined word opens the suggestions, and the keyboard stays open. A long press still selects the word as before. The keyboard most likely closed because Chrome's suggestion menu opened while the keyboard was still coming up, and the first tap no longer does both at once.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Update notice for Obeya run from a git clone</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/tell-source-users-when-they-can-git-pull-c5f66c/"/>
<id>https://demos.obeya.si/tell-source-users-when-they-can-git-pull-c5f66c/</id>
<published>2026-10-18T07:32:07.417Z</published>
<updated>2026-10-18T07:32:07.417Z</updated>
<summary type="text">If you run Obeya from a clone of the repository, it now checks the clone's upstream when it starts and then once an hour.</summary>
<content type="html">&lt;p&gt;If you run Obeya from a clone of the repository, it now checks the clone's upstream when it starts and then once an hour. When new commits that change code are waiting, the bar shows how many there are and offers a &amp;quot;git pull&amp;quot; button, just like the installed app's update notice. Hover over the notice to see the commits. Click the button and Obeya pulls them and restarts on the new code, waiting until running agents and any recording are finished. If local commits or uncommitted edits make a clean pull impossible, there's no button, and the hover explains why and what to do.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Replies you watch arrive are no longer marked as new</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/message-that-arrives-while-the-conversat-2597c9/"/>
<id>https://demos.obeya.si/message-that-arrives-while-the-conversat-2597c9/</id>
<published>2026-10-17T19:31:38.809Z</published>
<updated>2026-10-17T19:31:38.809Z</updated>
<summary type="text">Until now, an agent's reply that arrived while you had its conversation open still got the orange &quot;new&quot; edge, as if you had missed it.</summary>
<content type="html">&lt;p&gt;Until now, an agent's reply that arrived while you had its conversation open still got the orange &amp;quot;new&amp;quot; edge, as if you had missed it. Now a message that arrives while the conversation is open and the page is in view counts as read and gets no edge. Messages from before you opened the conversation, and those that arrive while the page is hidden (another tab, a locked screen), are still marked as new. Obeya's own chat sheet works the same way now: an answer that arrives while the sheet is open is read, without the edge.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Agents can wait for another task to finish, not just for a set time</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/snooze-until-another-task-reaches-a-stat-a28e6b/"/>
<id>https://demos.obeya.si/snooze-until-another-task-reaches-a-stat-a28e6b/</id>
<published>2026-10-17T19:30:53.998Z</published>
<updated>2026-10-17T19:30:53.998Z</updated>
<summary type="text">Until now, an agent that depended on another task could only snooze until a set time, then check whether the other task was done.</summary>
<content type="html">&lt;p&gt;Until now, an agent that depended on another task could only snooze until a set time, then check whether the other task was done. Often it wasn't, or the agent woke up long after it could have carried on. Now an agent can snooze until another card reaches a state, such as done, stopped or archived, and it wakes up as soon as that happens. When a snoozed card comes back, its log now says why: the other task is done, the time has come, you brought it back, there's something new for the agent (a review, a landing, a failed check), or the card needs you. Before, the log only said who had snoozed it.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Answered questions no longer look open</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/answered-question-in-a-task-s-conversati-151b4b/"/>
<id>https://demos.obeya.si/answered-question-in-a-task-s-conversati-151b4b/</id>
<published>2026-10-17T16:55:43.813Z</published>
<updated>2026-10-17T16:55:43.813Z</updated>
<summary type="text">Before, once you answered an agent's question in a task's conversation, the question still had an orange edge.</summary>
<content type="html">&lt;p&gt;Before, once you answered an agent's question in a task's conversation, the question still had an orange edge. That made it look as if it still needed you. Now an answered question loses the orange edge, and only its &amp;quot;Agent · Question&amp;quot; label stays orange to show you had something to do there. The orange edge marks only messages that are new to you, so it's easier to see what still needs your attention. A question the task is still waiting on looks the same as before: it stays at the end of the conversation with its answer options.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Demo videos show at full size as soon as a card opens</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/demo-video-on-an-opened-task-shows-as-a-7ef4f5/"/>
<id>https://demos.obeya.si/demo-video-on-an-opened-task-shows-as-a-7ef4f5/</id>
<published>2026-10-17T16:32:16.227Z</published>
<updated>2026-10-17T16:32:16.227Z</updated>
<summary type="text">When you open a card with a demo video that has no poster image, the video now shows at its full size with its first frame.</summary>
<content type="html">&lt;p&gt;When you open a card with a demo video that has no poster image, the video now shows at its full size with its first frame. Before, it appeared as a small, flat black strip and only grew to its real size once you pressed Play. That happened because the browser sizes a video that hasn't played yet by its poster, and these videos didn't have one. The player now takes the video's proportions from the file itself, so the video keeps the right size even when a poster is missing or fails to load. Videos that have a poster look the same as before.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Obeya's answer no longer pops up while you're reading the main chat</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/no-pop-up-for-obeya-s-answer-while-the-o-c85993/"/>
<id>https://demos.obeya.si/no-pop-up-for-obeya-s-answer-while-the-o-c85993/</id>
<published>2026-10-17T16:02:53.088Z</published>
<updated>2026-10-17T16:02:53.088Z</updated>
<summary type="text">When you ask Obeya something in the main chat, its answer used to show up twice: in the chat, and as a short white-on-black pop-up above the microphone.</summary>
<content type="html">&lt;p&gt;When you ask Obeya something in the main chat, its answer used to show up twice: in the chat, and as a short white-on-black pop-up above the microphone. With the main chat open, the answer now appears only in the chat, because you're already reading it there. This holds for answers that come right away, answers Obeya looks up and sends later, and answers that arrive after a usage limit lifts, on the desktop and on the phone. Answers that come with an Undo action still pop up, since the chat has no Undo button of its own, and so do error messages.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Phone: room below “Nothing waits for you.”</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-too-little-space-below-nothin-3c9ad2/"/>
<id>https://demos.obeya.si/phone-view-too-little-space-below-nothin-3c9ad2/</id>
<published>2026-10-17T14:54:06.363Z</published>
<updated>2026-10-17T14:54:06.363Z</updated>
<summary type="text">On the phone, the line &quot;Nothing waits for you.&quot; under &quot;For you&quot; used to sit right on top of the first snoozed card below it, so the two looked stuck together.</summary>
<content type="html">&lt;p&gt;On the phone, the line &amp;quot;Nothing waits for you.&amp;quot; under &amp;quot;For you&amp;quot; used to sit right on top of the first snoozed card below it, so the two looked stuck together. Now the cards start a little further down, with the same gap that separates the cards from each other. The section is easier to read, and it's clearer where the message ends and the snoozed cards begin.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Unread messages are marked in a card's conversation</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/mark-unread-messages-in-a-task-s-convers-1de82c/"/>
<id>https://demos.obeya.si/mark-unread-messages-in-a-task-s-convers-1de82c/</id>
<published>2026-10-17T14:53:14.503Z</published>
<updated>2026-10-17T14:53:14.503Z</updated>
<summary type="text">When you open a card, its new messages now have the same orange left edge that Obeya's main chat uses for answers you haven't read yet.</summary>
<content type="html">&lt;p&gt;When you open a card, its new messages now have the same orange left edge that Obeya's main chat uses for answers you haven't read yet. A message counts as new if it arrived after you last had that conversation in view and after your own last message. The marking stays until you close the card, so you can see what came in while you were away. It works the same on every kind of card, on the desktop and on the phone. Each browser keeps its own record of what you've read, so a message you read on the phone still shows as new on the desktop.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Highlight labels in demo videos stay inside the picture</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/demo-video-highlight-label-cut-off-at-th-72da8d/"/>
<id>https://demos.obeya.si/demo-video-highlight-label-cut-off-at-th-72da8d/</id>
<published>2026-10-17T14:35:23.969Z</published>
<updated>2026-10-17T14:35:23.969Z</updated>
<summary type="text">Before this change, a highlight's label in a demo video always started at the left edge of its highlight and stayed on one line.</summary>
<content type="html">&lt;p&gt;Before this change, a highlight's label in a demo video always started at the left edge of its highlight and stayed on one line. A label for a highlight near the edge of the video could end up half outside the picture. Now the label always stays fully inside the video. Near the right edge it moves left until it fits, and if it would go past the top it moves below its highlight. A label wider than the video wraps onto two lines. Videos rendered before this change still show the cut-off label until they are rendered again.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Phone list: tasks stay visible while their agent works on your note</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-a-task-vanishes-from-the-list-8eb80e/"/>
<id>https://demos.obeya.si/phone-view-a-task-vanishes-from-the-list-8eb80e/</id>
<published>2026-10-17T14:33:15.487Z</published>
<updated>2026-10-17T14:33:15.487Z</updated>
<summary type="text">On the phone, a task you sent a note to while it waited for your review used to drop out of the list.</summary>
<content type="html">&lt;p&gt;On the phone, a task you sent a note to while it waited for your review used to drop out of the list. It showed under neither &amp;quot;For you&amp;quot; nor &amp;quot;Running&amp;quot; until its agent handed it over again. Now it shows under &amp;quot;Running&amp;quot; with its status line and &amp;quot;Agent working on your note&amp;quot;, and it moves back to &amp;quot;For you&amp;quot; once the agent is done. A task you have just approved also stays under &amp;quot;Running&amp;quot; while it waits to be merged, so it no longer drops out of the list for a moment.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Agents can take back their own suggestions</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/agents-can-withdraw-or-supersede-their-o-6bd7b5/"/>
<id>https://demos.obeya.si/agents-can-withdraw-or-supersede-their-o-6bd7b5/</id>
<published>2026-10-17T14:32:02.887Z</published>
<updated>2026-10-17T14:32:02.887Z</updated>
<summary type="text">An agent that suggests a new task and later finds its reasoning was wrong can now withdraw that suggestion, or name a newer one that replaces it.</summary>
<content type="html">&lt;p&gt;An agent that suggests a new task and later finds its reasoning was wrong can now withdraw that suggestion, or name a newer one that replaces it. Until now it could only say so in its message, so both suggestions stayed on the canvas and both could be started. A suggestion you haven't accepted yet now disappears from the canvas right away. If you already accepted it, the card stays and is marked &amp;quot;replaced by …&amp;quot; or &amp;quot;withdrawn by the agent&amp;quot;, it shows up as needing you and sends a notification. You then choose to remove it, which stops its work and can be undone, or to keep it.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Long text in the chat field gets the full width</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-chat-input-s-buttons-side-by-f37289/"/>
<id>https://demos.obeya.si/phone-view-chat-input-s-buttons-side-by-f37289/</id>
<published>2026-10-17T14:26:42.108Z</published>
<updated>2026-10-17T14:26:42.108Z</updated>
<summary type="text">When you write or dictate a longer message in the field under a conversation, the screenshot, microphone and Send buttons now stack in a narrow column at the bottom right instead of sitting side by side.</summary>
<content type="html">&lt;p&gt;When you write or dictate a longer message in the field under a conversation, the screenshot, microphone and Send buttons now stack in a narrow column at the bottom right instead of sitting side by side. The text gets the width they free, which on the phone means noticeably more words per line and less scrolling. Short text keeps the buttons side by side as before, and the switch between the two layouts happens without jumping back and forth while you type, delete or dictate. The placeholder stays fully readable, and the thin scrollbar that used to show beside the buttons is gone. This applies everywhere the field appears, on the phone and on the desktop.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Swipe pop-ups away on the phone</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-swipe-obeya-s-pop-up-aside-to-a484a8/"/>
<id>https://demos.obeya.si/phone-view-swipe-obeya-s-pop-up-aside-to-a484a8/</id>
<published>2026-10-17T13:46:11.866Z</published>
<updated>2026-10-17T13:46:11.866Z</updated>
<summary type="text">On the phone, you can now dismiss Obeya's black pop-ups above the microphone by swiping them left or right.</summary>
<content type="html">&lt;p&gt;On the phone, you can now dismiss Obeya's black pop-ups above the microphone by swiping them left or right. This works both on the canvas and on an open card. It applies to Obeya's replies, to confirmations with an undo button and to a command that is still being read. Until now these pop-ups stayed on screen and covered part of the view until they went away by themselves. When a pop-up appears it nudges briefly to the side to show it can be swiped, and it stops doing that once you have swiped one away. The desktop stays unchanged.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">The video menu (⋮) opens again</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-demo-video-s-overflow-menu-do-111adc/"/>
<id>https://demos.obeya.si/phone-view-demo-video-s-overflow-menu-do-111adc/</id>
<published>2026-10-17T13:44:57.110Z</published>
<updated>2026-10-17T13:44:57.110Z</updated>
<summary type="text">The ⋮ menu in a demo video's controls opens again, on the phone and on the desktop, so you can download the video, turn on captions, change the playback speed or use picture-in-picture.</summary>
<content type="html">&lt;p&gt;The ⋮ menu in a demo video's controls opens again, on the phone and on the desktop, so you can download the video, turn on captions, change the playback speed or use picture-in-picture. Before, a tap or click on ⋮ did nothing visible: the menu closed again the moment it opened. That happened because the page took keyboard focus back from the video so the arrow keys could jump through it, and losing focus shut the menu. Now the arrow keys still jump through the video after a click, and the menu stays open.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Phone checks in real Chrome on an Android emulator</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/script-scripts-android-phone-ts-for-chec-37a32d/"/>
<id>https://demos.obeya.si/script-scripts-android-phone-ts-for-chec-37a32d/</id>
<published>2026-10-17T13:44:08.296Z</published>
<updated>2026-10-17T13:44:08.296Z</updated>
<summary type="text">A new script, bun scripts/android-phone.ts, lets agents test the phone view in real Chrome on an Android emulator.</summary>
<content type="html">&lt;p&gt;A new script, bun scripts/android-phone.ts, lets agents test the phone view in real Chrome on an Android emulator. That covers what a desktop headless browser can't reproduce: the on-screen keyboard, video fullscreen and screen rotation. With one command each, an agent can boot the emulator, open Obeya on it, tap elements with real touches, type, rotate the screen, read values from the page and take screenshots or recordings. Every wait inside the script has a time limit. Until now agents built their own emulator helpers for each check, which took up most of their work and often stalled. Phone fixes like the chat input with the keyboard open can now be checked faster and more reliably.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Flick the phone's conversation panel up or down</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/phone-view-fling-the-chat-panel-up-or-do-67fdfd/"/>
<id>https://demos.obeya.si/phone-view-fling-the-chat-panel-up-or-do-67fdfd/</id>
<published>2026-10-17T12:52:27.931Z</published>
<updated>2026-10-17T12:52:27.931Z</updated>
<summary type="text">On the phone, you can now throw the conversation panel instead of dragging it all the way.</summary>
<content type="html">&lt;p&gt;On the phone, you can now throw the conversation panel instead of dragging it all the way. If you let go while your thumb is still moving, the panel keeps going in that direction and slows down. A short swipe up opens it to full height, and a short swipe down closes it. If you stop your thumb before lifting it, the panel stays exactly where you left it, so you can still set any height you like. Resizing becomes a quick one-handed flick, much like scrolling on the phone.&lt;/p&gt;</content>
</entry>
<entry xml:lang="en">
<title type="text">Proposals from the work retrospective can be accepted again</title>
<link rel="alternate" type="text/html" href="https://demos.obeya.si/proposals-from-the-work-retrospective-ca-1de686/"/>
<id>https://demos.obeya.si/proposals-from-the-work-retrospective-ca-1de686/</id>
<published>2026-10-17T12:36:53.886Z</published>
<updated>2026-10-17T12:36:53.886Z</updated>
<summary type="text">Proposals that the work retrospective puts on the canvas can be accepted again with &quot;Übernehmen und starten&quot;, &quot;Übernehmen&quot; or &quot;Als Idee besprechen&quot;.</summary>
<content type="html">&lt;p&gt;Proposals that the work retrospective puts on the canvas can be accepted again with &amp;quot;Übernehmen und starten&amp;quot;, &amp;quot;Übernehmen&amp;quot; or &amp;quot;Als Idee besprechen&amp;quot;. Since a recent change, accepting them failed with &amp;quot;This is no longer a proposal.&amp;quot; The card still stayed a proposal in For You. Those proposals lacked details that agents' proposals always carry, and the check stumbled over the gap. Accepting now works for every proposal, including the ones already waiting on the canvas, so they can be started as usual.&lt;/p&gt;</content>
</entry>
</feed>
