ShipJul 23
Run and touch a live iOS Simulator inside Studio
The Chat right rail in Pathrule Studio now holds a real, interactive iOS Simulator, not a screenshot. Pick an available simulator and run the current Expo, React Native, Flutter or native Xcode/Swift app, then tap, drag, swipe, long-press, type and hit the system buttons directly inside Pathrule. The panel sits in a Simulator and Context accordion above Code, Memories, Rules, Skills and Signals, so you can collapse it and come back without losing either side's state. The active Studio agent shares the exact same live simulator session: ask it to inspect or operate the running app and watch it work, then take over the instant you touch the screen. Hand the frame you are looking at straight into the chat as visual context. Runs on Apple Silicon with Xcode.
ShipJul 23
Your MacBook notch becomes a live Studio companion
Pathrule Studio now lives in the MacBook notch. Whenever an agent is running, calling out for your answer, or approaching a usage cap, the notch surfaces it no matter which workspace, conversation, model or engine it belongs to. Glance at every in-flight conversation at once, answer a waiting question inline without switching windows, stop a run or jump straight to the conversation, and read live usage against your provider caps. It is native for a smooth overlay and ships inside the app, so there is no separate install and no second account or device to set up. It stays end to end encrypted like the rest of Studio: conversation content reaches the notch already decrypted on your own machine, and the companion never touches the server or holds a key.
ShipJul 23
Run any app in your monorepo, and let your agent launch it
Studio's Run now understands a whole monorepo. It discovers every runnable target across your workspace, from Expo and React Native to Flutter and native Xcode apps, and merges a shared run catalog your team can commit with the target and device you pick locally. New in this release, Run is available to the agents themselves: an assistant can select a target and launch it for you through Pathrule's run tools, so "run the app and check the login screen" becomes something your agent can actually do. A cleaner target and device picker makes switching between apps and simulators a single click.
ShipJul 23
Pathrule Signals: your running product talks back to your agents
Signals closes the loop between a running product and the AI that builds it. In Pathrule Studio it watches your product's real runtime events in the background and turns the ones that matter into context your agents already understand. It is deterministic, not another analytics engine: repeats of the same problem are grouped into a single incident, and only when one crosses a worthiness threshold does Signals hand it to your existing task flow, with a Context Brief that names what happened, where it maps in your code, and the exact rules and memories that touch it. After your next release it watches the same incident and reports an honest outcome, observing, quiet, verified or recurred, so a fix is marked done only when real runtime evidence backs it up. Signals never blocks or crashes your product: transport and quota failures are swallowed and nothing is thrown into your app. See Signals overview.
ShipJul 23
Turn Signals on in Studio with a guided /signals setup
Signals is opt-in and lives entirely in Pathrule Studio, per workspace. Run /signals and Pathrule does a read-only scan of your project, then proposes exactly where runtime instrumentation should go, one point at a time. You approve the points you want and Studio wires the connection in for you, with no package to install and no keys to copy by hand. Consent is explicit and follows you across devices, so turning Signals on for a workspace on your Mac carries over everywhere you work. Each incident then appears in the Signals view with its status, what happened, where it mapped, the context that was supplied and any runtime outcome, and it shows up in your knowledge graph and the path's right rail alongside the memories and rules it relates to. See Setting up Signals and Plans, quotas and retention.
ShipJul 18
Antigravity joins Pathrule Studio as a first-class engine
Pathrule Studio on macOS now runs Google Antigravity alongside Claude Code, Codex, Grok, Kimi and OpenCode. Choose Antigravity for a chat, task or plan and it receives the same path-scoped memories, rules and skills as every other Studio engine. Conversations resume with their Antigravity context intact, supported models appear in the regular engine picker, and usage stays visible in the same place as the rest of your coding agents.
FixJul 18
Browser sign-in can no longer strand your message
When an engine needs browser sign-in, the waiting card now shows the exact authorization address in a selectable field with a copy button. If macOS or the engine cannot open the browser, paste the link into any browser and finish there. Your original message stays queued and sends when the engine is ready. Studio also distinguishes a real sign-in failure from a temporary timeout or command error, so an already working account is not pushed into a login loop.
UXJul 18
Every answer keeps the engine that produced it
Switch from one coding engine to another inside the same conversation and earlier answers now keep their original engine and model identity. The labels survive a restart and stay accurate when the conversation is opened from another device, so a mixed-engine thread remains easy to follow. A new prompt waits for the current answer to finish, then moves to the engine you selected without replacing the conversation or losing its history.
PerfJul 18
Smoother streaming and safer engine handoffs
Long answers render more smoothly while rapid text and reasoning updates arrive, and queued prompts move into the transcript only when an engine has actually accepted them. Engine changes now settle at a clear turn boundary, retries keep the same user message, and interrupted sign-in or handoff work is cleaned up instead of leaving the chat stuck in a waiting state.
ShipJul 17
Kimi joins Pathrule Studio as a first-class engine
Pathrule Studio on macOS now runs Kimi alongside Claude Code, Codex, Grok and OpenCode. Start a thread with Kimi and it plugs into the same engine picker, sign-in and readiness checks as every other engine, with the same path-scoped memories, rules and skills Studio already delivers to the assistant before the first tool call. There is no new subscription: Pathrule connects to the coding agents you already run.
UXJul 17
Switch engines mid-chat without losing your place
Changing the engine on a fresh chat in Pathrule Studio now prepares the new engine in the background and swaps it in only when it is ready, so your view never flickers or resets while you keep typing. The switch happens in place: the conversation you were looking at stays put until the replacement engine is live, then hands over without a jarring reload.
FixJul 17
Live sessions that hold on to your work
A wave of reliability fixes lands across Pathrule Studio's live sessions. Messages you send while a turn is still running are now queued and delivered in order instead of being silently dropped, and Studio verifies the connection before it dispatches so a prompt never vanishes into a dead session. When a run is interrupted, Studio classifies why and lets you retry it cleanly, and it can recover a whole conversation even after you have switched engines mid-thread. Recovery prompts settle in place without flicker, and every message reliably promotes to the right spot instead of getting wedged between states.
FixJul 17
Sign-in, recalls and prompts that behave
Connecting an engine is far more forgiving: an interrupted or re-prompted login now recovers and stays retryable instead of wedging the chat, and Studio confirms a native provider login before it trusts it. Recalled context from earlier turns is kept on its own turn so it no longer bleeds into the message you are writing, and answers to interactive prompts render as their own cards instead of leaking into chat bubbles. The knowledge panel shows a memory, rule or skill cleanly without repeating its name and description a second time, and searching skills matches on the skill name instead of surfacing unrelated text.
ShipJul 17
Save a mirrored Studio design straight from your phone
The design mirror on iOS can now hand you the picture. While you follow a Pathrule Studio design live on your iPhone, export the frame you are looking at as an image and share or save it in a tap, without leaving the app. Older desktops that predate the fit hint still mirror phone and tablet layouts at the right width, so a native app screen reads like the running app rather than a shrunken thumbnail. It stays end to end encrypted: only the rendered design reaches your phone, never your source code.
ShipJul 16
Grok joins Pathrule Studio as a first-class engine
Pathrule Studio on macOS now runs Grok Build alongside Claude Code, Codex and OpenCode. Start a thread with Grok, switch engines mid-conversation without losing the work you have built, and use the same path-scoped memories, rules and skills the rest of Studio already delivers. Sign-in and readiness checks match the other engines, so Grok shows up in the same engine picker, preflight and usage surfaces rather than as a bolted-on side path.
ShipJul 16
Plans you can read, follow and run inside the chat
When an assistant produces a plan in Pathrule Studio, it no longer lives only as a wall of markdown. Studio turns it into a structured plan you can read step by step, keep open while the work runs, and hand off into the task board without retyping. The plan stays attached to the conversation, so you can revisit it, refine it, or run the next step without hunting through earlier messages.
UXJul 16
Design knows when you are revising versus starting over
The Design surface now asks a clear intent question before the assistant rewrites a frame: keep going on the current design, or start a new one. That stops a revise request from wiping work you meant to iterate on, and it keeps a fresh brief from fighting the last canvas. The choice is explicit, so a short note like "make the header denser" stays a revision, and "new onboarding screen" opens a clean start.
UXJul 16
A guided first run in Studio, in the language you pick
Opening a new project in Pathrule Studio now greets you inside the chat itself, not as a separate tour. Pathrule walks you through what Studio does, which engines it found on your machine, and a one-tap project scan that seeds useful knowledge for the folder you opened. A locale picker sits in that first conversation, so the whole onboarding (and your preferred reply language) can start in English, Turkish or the other languages Studio supports, before you write a single prompt.
ShipJul 16
See which knowledge shaped a turn, and dismiss recalls that miss
Every Studio turn now shows a clearer context strip: which memories, rules and skills Pathrule actually delivered, with a plain "proven here" signal for knowledge that has already helped in this project. Recalled past turns appear as tidy cards you can accept or reject. A reject sticks across reopens and across your devices, so a recall you dismissed on the Mac stays dismissed on the next session instead of coming back every time you open the thread.
ShipJul 14
Animate your Studio designs, right on the canvas
The Design surface in Pathrule Studio can now bring a design to life. Add motion to any frame and choreograph how elements enter and move on a visual timeline, with named easing presets so everything shares one feel. Play an animation on load, on hover, or as the page scrolls, and preview it live as you tune the timing. Save a look you like into a reusable motion library and drop it onto other designs in a click, or just describe the motion you want and let the design assistant build it. Animations ride along inside an exported design file, so a design plays back the same way wherever you open it.
FixJul 14
Studio picks up exactly where you left off
Quit Pathrule Studio, restart your Mac, or hit an unexpected crash, and Studio now offers to restore your session so you come back to the work in progress instead of a blank slate. Each surface is isolated on its own too, so if one view runs into trouble it recovers in place rather than taking the whole app down with it, and the order you arranged your workspaces in stays put between launches.
ShipJul 10
Watch your Studio designs come to life on your phone
The designs you build in Pathrule Studio on macOS now mirror to your iPhone, full screen and live. Open the mirror and swipe between screens like slides, and it follows your Mac as you work: select a frame in Studio and your phone jumps straight to it. App designs render at real device width, top-aligned and scrollable, so an iPhone or Android layout reads exactly like the running app, while web, presentation and social designs fit the whole artboard on screen. The chrome sits over the design and auto-hides, so a tap gives you the whole screen back to the work. It stays end to end encrypted like the rest of your session: only the rendered design streams to your phone, never your source code.
ShipJul 10
Run your task board from your phone
The Pathrule Studio task board is now on iOS. Lay your work out across the lanes and drag a card between them with a smooth, Trello-grade lift that never fights the scroll. Open any card to read or edit its prompt, then hand it to your agent to run or ask for a plan, all from your phone. The board is shared with your team and updates live across every device, so a card you move on the Mac lands in the right lane on iOS, and a run you start follows along. Each card's prompt and attachments are end to end encrypted exactly like everywhere else in Pathrule: your machine holds the key and only ciphertext leaves your device.
ShipJul 9
Build a real design system in Studio, with variables and styles
The Design surface in Pathrule Studio gains a full design-system layer. Define variables once, colors, spacing, radius and your type scale, then apply them across every screen, and bind any color, font, size or spacing straight to a variable so a change in one place updates everywhere it is used. Color variables carry light and dark modes, so a single switch reflows the whole design between themes. Bundle a whole typographic or shadow treatment into a text or effect style and apply it in one click. Organize everything into libraries and attach the ones a design should use. You can seed a system from your project's own brand in one step, import a .tokens.json file, or build one from scratch, and once a library is attached the design assistant works in your tokens instead of arbitrary values.
ShipJul 9
Reusable components and variants come to Studio design
Turn any part of a design into a reusable component and drop instances of it anywhere, each one linked to its master so editing the master updates every copy at once. Components carry real properties you set per instance from the inspector: a text slot, a switch to show or hide a part, a color, a number, or a swap that drops a different component into a slot. Group related looks into variants, default, hover, active, disabled or sizes, and switch between them from a single dropdown, with sibling designs folded into one variant set for you. You can also author a whole component in words: ask the design assistant with @components and it generates the component, its properties and its variants, grounded in your design variables. Components and variants ride along inside an exported design file, so nothing comes unlinked when you share or reopen it.
ShipJul 7
Pathrule for iOS is here, on the App Store
The Pathrule iOS companion is out of coming-soon and live on the App Store. Your whole AI coding workspace now travels with you: start new tasks, reply to existing sessions, and follow your agents as they think, plan and edit files in real time, all from your phone while your source code stays on your Mac. Watch a run live, answer a permission prompt or a question from either device, and browse the memories, rules and skills attached to every repository path exactly as your agents receive them. Every connection between your iPhone and Mac is end to end encrypted and the keys never leave your devices, so only your team's knowledge and the live session stream sync, never your code. Pathrule for iOS is the companion to Pathrule Studio on macOS: install Studio, sign in with the same account, and your workspaces, agents and live sessions are with you anywhere.
ShipJul 4
Turn a chat into a live design, without leaving the conversation
Ask an assistant in Pathrule Studio for a brand-new screen or layout and it no longer answers with a wall of code. It offers to build the design as a live Pathrule Artifact instead: one click and the design comes to life right in the conversation, with a link that stays live for 7 days. Open any artifact full screen to look closely, copy the link, or open it in the browser. On a Team plan you can transfer an artifact straight into the Design surface to keep it permanently and keep iterating. The offer reads your intent in any language, so it works whether you ask in English, Turkish or Japanese, and it only shows up for a fresh request, never when you are already refining an existing design.
ShipJul 4
See your whole workspace as a knowledge graph
The Summary surface gains a Graph tab: a fluid, force-directed map of your workspace, with every folder node linked to its memories, rules and skills, and memories linked to each other through the connections you write between them. Zoom and pan across it, hover a node to light up its neighbours, and watch labels fade in as you move closer. The overview tab now carries a small live preview of the graph that you can click to open the full canvas, and the whole Summary refreshes on its own so the picture stays current as your team's knowledge grows.
ShipJul 4
See and comment on your team's designs, privately
On a Team plan, the designs your teammates make in Pathrule Studio now appear in a shared team library, so you can open a colleague's design, watch it update live, and leave comments right on it, all inside the app and all within your organization. No public link is created and nothing is published to the web: this is a private, members-only view that sits alongside the anonymous share link for when you do want to send something outside. Solo work stays exactly as it was, on your own machine.
ShipJul 4
Screenshots reach every engine that can see them
When you attach a screenshot, a mockup or a diagram, Pathrule now hands it to whichever engine you are running, Claude Code, Codex or OpenCode, as real visual context instead of dropping it. Images are only forwarded to models that can actually see, so a text-only model never receives a picture it cannot read, and the design assistant can check its own work against the image you gave it.
FixJul 4
An interrupted run picks up where it left off
If a running task is cut short by a restart, a lost connection or a crash, Pathrule now recovers the session and resumes it instead of losing the work, across Claude Code, Codex and OpenCode. The conversation shows when a thread can be resumed, so you carry on from where the agent stopped rather than starting the whole task over.
ShipJul 3
Plan and run your work on a board, now with images on every card
Pathrule Studio has a task board. Lay out your work as a column of cards, hand any card to Claude Code, Codex or OpenCode to run, and watch it move across the board as it works. New in this release, a card can carry images. Paste or drop a screenshot, a mockup or a diagram onto a card and it rides along when the card runs, handed to the agent as real visual context instead of a description you have to type out. You choose which engine a board runs on, start a card on its own, and follow progress live across your devices. Card images are end to end encrypted exactly like the card's prompt: your machine holds the key and the server only ever stores ciphertext, so a card can show it has images without anything readable leaving your device.
ShipJul 3
Design surface: export to PNG, hand a design into chat, and see who left each comment
The Design surface gains three things. You can export any design to a PNG in one step, ready to paste into a doc, a ticket or a message. You can also hand a design straight into the chat as a snapshot, so you can point the assistant at what it just made and ask for the next change in plain words instead of re-describing the screen. And on a shared design, comments now carry a colored avatar with the commenter's initials, picked so the same person keeps one color across pins and sessions, which makes a busy review easy to read at a glance. The first run is richer too, opening on a small gallery of sample interfaces so you can see the breadth of what it produces.
ShipJul 2
Share a design as a private, read-only link
You can now turn a design in Pathrule Studio into a link that anyone can open in the browser, with no account needed. The page renders the design read only, plays it as a presentation, and, when you allow it, lets viewers leave pinned comments that appear live. Sharing is zero knowledge: the content is encrypted before it leaves your machine and the key travels in the link itself, so the server only ever stores ciphertext. You choose per link whether comments and source download are allowed, and you can revoke a link at any time. The viewer runs on its own isolated address so it never touches your account session, and shared pages are kept out of search engines.
UXJul 2
Studio design surface: a richer first run and live share comments
The Design surface now greets you with a small gallery of sample interfaces so a first-time user sees at a glance the breadth of what it produces. Comments on a shared design now persist and push live to everyone viewing, edits and deletes sync across devices, and undo and redo are a click away. Board settings and the task board got a round of polish so the workbench feels more finished.
PerfJul 2
Agents update your knowledge with small edits, not full rewrites
When an assistant changes an existing memory or rule, it can now send just the edit, an append, a targeted replace, or a whole section, instead of resending the entire body. That means less back and forth and fewer tokens on every knowledge update, across Claude Code, Cursor, Codex, Windsurf, the desktop app and the hosted connector.
