Artifacts: Share a Design, Gather Comments, Resolve Them with AI
A design is not finished when it is drawn.
It is finished when the team has seen it, said what is wrong, and had it fixed.
Artifacts is the layer where that whole loop happens on the design itself.
What this covers
- Artifacts is the layer where designs built in the Design surface and in chat become shareable objects a team and outside reviewers can comment on.
- A shared artifact collects comments in one panel: your own notes, live team comments, and comments left by anyone with a public link.
- Any comment can be handed straight to the AI to resolve as a scoped edit, so feedback turns into a revision without leaving the artifact.
- Public links are zero-knowledge encrypted, update live, and are created only on an explicit share action, with free links expiring after seven days.
Before and after
| Area | Design feedback the usual way | Feedback on the artifact itself |
|---|---|---|
| Where a comment lands | A Slack thread or a marked-up screenshot | Pinned on the exact element of the live design |
| Who can weigh in | Whoever has the file or the tool open | Teammates in the app and anyone with the link |
| What a comment produces | A task for a human to do later | A scoped edit the AI can resolve on the spot |
| What the reviewer sees | A static image that may already be stale | The live design, updating as edits land |
A design is not done when it is drawn
AI made the generating part fast. You can turn a sentence into a polished screen in the Design surface, or ask for one in chat, and have something finished-looking in seconds. That was the hard part for years, and it stopped being the hard part.
The slow part moved to review. A design still has to be seen by the people who care: the designer who owns the system, the engineer who has to build it, the founder who has an opinion about the hero. Their feedback lives somewhere else entirely, in a Slack thread, on a screenshot someone drew arrows on, in a meeting nobody wrote down.
So the feedback and the design drift apart. The comment says fix the spacing on the second card, and by the time someone acts on it the design has changed, or the comment is lost, or it becomes a ticket that ages. Artifacts is built to close that gap by keeping the feedback on the design itself.
What Artifacts is
An artifact is a design made shareable. The designs you build on the Design canvas, and the ones an assistant produces for you in chat, both become artifacts: self-contained, real designs you can put in front of other people, not screenshots of them.
Sharing has two reaches. Inside the app, a design can be synced to your team so other members open it, see it live, and comment on it. Outside the app, a design publishes to a link anyone can open in a browser, no account required, to review and comment. Same artifact, two audiences.
The point of making it an artifact rather than an export is that it stays live and it stays connected to its comments. A reviewer is not looking at a frozen picture from last Tuesday. They are looking at the current design, and what they say about it lands in a place the design can act on.
One place for every comment
Comments on an artifact come from three directions and land in one panel. There are your own local notes, the ones you leave for yourself while working. There are team comments, which every member of your org sees live the moment they are posted. And there are comments from a public share, left by whoever you sent the link to.
They are pinned, not filed. A comment attaches to the specific element it is about, so fix the label on this button is anchored to that button, not lost in a thread that describes it. Anyone reviewing can see exactly what each note refers to.
Bringing all three origins into one surface is the quiet part that matters. A designer leaving internal notes, a teammate reviewing in the app, and a client commenting on a public link are all writing on the same artifact, and the owner sees the whole conversation in one place instead of three tools.
Comments the AI can resolve
The part that makes this more than a review board is what a comment can do. A comment is a scoped instruction attached to a specific element, which is exactly the shape of input an assistant can act on. So you can hand a comment straight to the AI and have it resolve the comment as an edit to the design.
That changes the economics of feedback. Normally a comment is a promise that a person will do something later. Here, tighten this spacing or make this heading match the others can be resolved on the spot: the AI applies the change to the design, and the comment moves from open to handled. You still get to keep or reject; the AI does the mechanical part.
It also means a round of review does not have to become a backlog. A design collects ten comments from three people, and instead of ten tickets you work down the list, resolving the straightforward ones with the AI and reserving your judgment for the ones that need a human call.
Sharing that stays private until you decide
Reach does not come at the cost of control. A public link is only ever created when you explicitly share, never automatically, and it is zero-knowledge encrypted, so the server that hosts it only ever holds ciphertext. You can put a password on it. It updates live as you keep editing, and revoking it or deleting the design kills the link immediately.
The links are also disposable by default. On a free plan a share expires after seven days; on a paid plan it stays up as long as you want. When a link is gone, whether it expired or the owner took it down, a viewer does not hit a broken page. They get a branded card that says plainly that the link is no longer valid, and points them back to Pathrule.
A quick artifact from chat is the low-commitment entry point: the assistant can offer to turn a design request into a shareable artifact, and only builds it once you accept, so the cost of being ready is almost nothing. When one of those is worth keeping, you transfer it into the Design surface, where it becomes a design document you own, edit, and sync to the team like any other.
Why the artifacts carry your context
What keeps this from being a generic feedback tool is where the designs come from. An artifact made in the Design surface was generated on your team context layer: the same path-scoped memories, rules, and skills that shape your coding sessions also shaped the design, so it arrives already on-brand. Review starts from something that already knows your product, not from a stranger.
That makes the review loop tighter at both ends. The design shows up closer to right because it was made with your rules; the comments that remain are about taste and product calls, not the basics your context layer already enforced; and resolving those comments with the AI runs through the same engine, so the fixes stay on-brand too.
Every signup gets three months of Pathrule PRO on the house. If you want to put a real design in front of your team, gather comments, and resolve them without leaving the artifact, [email protected] is open.