Artifacts

Artifacts let you capture the output of a Syntic Code session and share it as a self-contained document. When Amara produces something worth keeping, a design writeup, a migration plan, a generated report, or a working snippet, you can promote it to an artifact instead of copying text out of your terminal. Artifacts preserve formatting, code blocks, and structure, and they carry a stable link you can hand to teammates.

Creating an artifact

During any session you can ask Amara to save its work as an artifact, or use the /artifact command to package the most recent output. Syntic Code renders the content, assigns it an identifier, and stores it so it survives after the session ends. You can create multiple artifacts from a single conversation, which is useful when a long task produces several distinct deliverables such as a summary, a checklist, and a patch.

# In an interactive session
/artifact create "Q3 migration plan"
 
# List artifacts from recent sessions
syntic artifact list

Sharing and reviewing

Each artifact has a shareable link that renders the document in a clean, read-only view. Because artifacts are decoupled from your terminal, colleagues can read them without running syntic themselves, which makes them a natural fit for reviews, handoffs, and status updates. Teammates who do have Syntic Code installed can open an artifact and continue the work, using it as the starting context for a fresh session.

When to use artifacts

Reach for artifacts when the value of a session is the output rather than the process. Planning documents, generated documentation, one-off reports, and reference snippets all make good artifacts. For work that belongs in your codebase, commit it as a file instead; artifacts are best for content that lives outside the repository or that you want to circulate before deciding where it should land.