<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Behavio</title>
    <description>The latest articles on DEV Community by Behavio (@behavio_ui_screen).</description>
    <link>https://dev.to/behavio_ui_screen</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4134159%2Fe5bc7680-90ef-4f9b-a765-ce2c7f2d325d.png</url>
      <title>DEV Community: Behavio</title>
      <link>https://dev.to/behavio_ui_screen</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/behavio_ui_screen"/>
    <language>en</language>
    <item>
      <title>Point at a UI change. Give your coding agent the context.</title>
      <dc:creator>Behavio</dc:creator>
      <pubDate>Sun, 20 Sep 2026 13:46:40 +0000</pubDate>
      <link>https://dev.to/behavio_ui_screen/point-at-a-ui-change-give-your-coding-agent-the-context-4082</link>
      <guid>https://dev.to/behavio_ui_screen/point-at-a-ui-change-give-your-coding-agent-the-context-4082</guid>
      <description>&lt;p&gt;When a designer says “remove these yellow icons,” the intent is clear to the person sitting in front of the screen. It is much less clear when a coding agent receives only a screenshot, a window title, and a sentence.&lt;/p&gt;

&lt;p&gt;I built UI Screen Context to close that gap.&lt;/p&gt;

&lt;h2&gt;
  
  
  The handoff
&lt;/h2&gt;

&lt;p&gt;Start a recording, point at the element, and speak. The app follows the active window as you work, records the pointer target, captures screenshots and timing, and transcribes speech locally on the Mac. When you stop, it creates a structured context folder that you can paste into a coding agent.&lt;/p&gt;

&lt;p&gt;The agent gets:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the recorded windows and their timing;&lt;/li&gt;
&lt;li&gt;pointer events and the text target when one can be confirmed;&lt;/li&gt;
&lt;li&gt;recommended evidence images;&lt;/li&gt;
&lt;li&gt;the original transcript and the speech language;&lt;/li&gt;
&lt;li&gt;clear limits when the capture cannot prove something.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last part matters. A brief window switch can be missed. A frame held during a transition is not proof that the UI changed. The export says this plainly so the agent has less room to guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why local?
&lt;/h2&gt;

&lt;p&gt;The capture and speech models run locally. The app can use macOS speech or a local Whisper model, including an existing model folder. The generated context keeps the language the user actually spoke instead of silently translating it to English.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who it is for
&lt;/h2&gt;

&lt;p&gt;It is useful when a product designer, developer, or QA person needs to show a change across a real interface and wants the agent to start with evidence rather than a long explanation. It is also useful for debugging the handoff itself: you can inspect exactly what the agent will see before asking it to edit code.&lt;/p&gt;

&lt;p&gt;The app is free and Apache-2.0 licensed.&lt;/p&gt;

&lt;p&gt;Source: &lt;a href="https://github.com/behavio1/behavio-context" rel="noopener noreferrer"&gt;https://github.com/behavio1/behavio-context&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Demo video:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/K5U635NP1BM" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;Website: &lt;a href="https://behavio.one" rel="noopener noreferrer"&gt;https://behavio.one&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’m sharing it because the format is still evolving. If you use coding agents for UI work, what is the one piece of context you wish they received every time?&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>macos</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
