Artifacts
An artifact is a mockup, a diagram or a clickable set of pages you work on with your agent. A draft belongs to one task; a lasting artifact is kept for the project.


Create and review
Ask "Using QL, show two layouts for the settings page." No workflow starts. A task's draft appears as a compact entry in Files.
Ask about a spot
Mark a spot to open the quick feedback field. Say what should change, add files or paste an image, then send it to the current agent. The request carries the artifact, page, spot and revision. Marking a spot never sends anything by itself.
Preview it
Switch Light, Dark, Desktop and Phone; F goes full screen. Buttons and links work, and pages may run their own scripts, but nothing loads from the network. Your agent checks each page in both themes and widths before you see it.
The Library


Artifacts in the sidebar holds the Library. Search by project, artifact or page, narrow with Filters, and switch between List and Gallery. Starred Favorites sit above the list. The row menu renames, copies, archives or deletes; Archived › Recently deleted restores.
Lasting artifacts
Keep a draft
Save to library… in a draft's menu stores it In the repository, where it travels with commits, or Only on this computer, out of Git. To change a lasting artifact, ask your agent to draft on it. Files keeps its source, metadata and revisions together. Restoring a revision keeps the artifact's identity; removing a registration never deletes the application source it points to.
Fold in at Verify
See what changed
Verify shows This task changes …; the original stays until then.Pick the pages
Compare shows both versions.Fold them in
Fold N pages in. They join the pull request only with a Git action you authorize.
Existing artifacts
Artifacts from earlier versions keep working. Their old share-link details, notes and attachments stay on your computer as read-only history.