Artifacts are durable, reusable outputs from agent work. They are saved separately from the chat and editable task description, so you can continue refining, referencing, downloading, or sharing useful work.
Use artifacts for work that should remain easy to find and reuse, including:
Markdown and HTML are common artifact formats. LatchLoop also supports plain text, JSON, and React artifacts when those formats better fit the output.
An agent can create an artifact when you ask for one or when preserving reusable work would be helpful. Unlike a message in the conversation, the artifact remains an independently accessible document associated with its source task and project.
Tell the agent what to preserve, which format you prefer, and how you expect to use it. For example:
“Create a Markdown artifact summarizing this research so we can reference it in another task.”
“Turn this implementation plan into an HTML artifact and update it as you complete each phase.”
The agent can update the same artifact as work progresses instead of creating a new copy each time. Ask it to revise, expand, or reorganize the existing artifact when you want to preserve a single source of truth.
Artifacts created for or linked to a task appear in that task’s Artifacts view. The main Artifacts library provides a cross-task place to find artifacts you can access. There you can search artifact titles and content or filter by project, format, or sharing status.
Artifacts keep their source task and project association, but you can open them independently.
To update an artifact yourself:
Markdown artifacts provide a rich editing experience. Other formats can be edited as source and previewed. Changes are saved to the artifact and appear everywhere that artifact is linked or viewed, including through an active public share link.
Choose Download to save an artifact with an extension appropriate to its format.
Referencing an artifact makes the same artifact available to later work without duplicating it:
@ and choose an accessible artifact from the suggestions.The artifact link is inserted into the description, and the artifact appears in that task’s Artifacts view. The agent can then use it as context for later work.
This reference points to the existing artifact rather than creating a copy. Future edits remain visible from every linked task. Access is still permission-aware: users and agents can only read artifacts available through the applicable task and project access.
Artifacts are private to the relevant LatchLoop project access by default. Teammates who can access the project can view its artifacts in LatchLoop.
An internal artifact link does not grant project access. If a teammate cannot access the artifact’s project, sending that internal link will not make the artifact available to them. Editing and sharing controls also depend on the person’s permissions.
When you have permission, you can publish an artifact with a public link:
Anyone with the public link can view the rendered artifact without signing in and can download it. The public page reflects later updates to the same artifact.
Public means anyone with the link can access the artifact’s contents. Review the complete artifact and remove confidential information before sharing it publicly.
Public-share management is available to authorized users, including the artifact or task owner, project owner, and team admins or owners. If Share is unavailable, ask a project owner or team admin or owner to create the link.
To disable access, open the artifact and select Unshare. The public link stops working immediately. Deleting the artifact also makes its public link unavailable.
Available actions depend on your permissions.
An artifact is not shown in a task
@, choose the artifact, and save the task.A teammate cannot open an internal artifact link
Share is unavailable or disabled
An old public URL no longer works