{"version":"2.1.323","anchor":"new-progress-ui-node-drawn-natively-only-by-mobile-client","canonical_anchor":"new-progress-ui-node-drawn-natively-only-by-mobile-client","heading":"Progress bars can now be sent to the mobile app","tier":"internal","area":"Mobile App","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/new-progress-ui-node-drawn-natively-only-by-mobile-client","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Progress bars can now be sent to the mobile app\n\nClaude Code can now describe a progress bar to a mobile app that can draw one; other apps and the terminal get plain text instead\n\n**What**\n\nClaude Code can now describe a progress element as part of the screens it sends to other apps. A progress element shows how far along a task is. It has a label, a value from 0 to 1, optional text for the value, and a colour.\n\n- A mobile app that says it can draw progress elements receives the progress element itself.\n\n- Any other app receives the same information as ordinary boxes and text.\n\n- In the terminal, the label is drawn dimmed, alongside the value written out as text.\n\nOn mobile, a progress element that is not on the list of elements the app can draw is now converted into something it can show. Before, it was dropped.\n\n**Why**\n\nThis prepares for real progress bars in the mobile app. If you use the terminal, you only see a text version.\n\n- Area: Mobile App\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}