Slay Artifacts

Artifacts are files attached to tasks, stored on disk at {data-dir}/artifacts/{taskId}/{artifactId}.ext. They can be text files, images, or any binary content. Use artifacts to attach specifications, screenshots, logs, or any reference material to a task.

The --task flag defaults to $SLAYZONE_TASK_ID for create, upload, and mkdir. Note: list requires an explicit task ID argument.

Files

• slay tasks artifacts list <taskId> [--json] [--tree] — list all artifacts for a task.

  • --tree shows an indented folder structure

• slay tasks artifacts read <artifactId> — output artifact content to stdout.

  • Binary artifacts (images, etc.) are written as raw buffers
  • Text artifacts as UTF-8

• slay tasks artifacts search <query> [--task <id>] [--all-tasks] [--folder <id>] [--titles-only] [--content-only] [--regex] [--case-sensitive] [--limit <n>] [--max-matches <n>] [--json] — search artifact titles and file contents.

  • Default: substring match, case-insensitive, scans both titles and contents
  • Requires --task (or $SLAYZONE_TASK_ID) unless --all-tasks is set
  • --regex treats query as a JS RegExp; invalid regex exits 1
  • Binary artifacts (images, PDFs, ZIPs) skip content scan automatically
  • Files >5MB skip content scan with a stderr warning
  • Default limit: 50 artifacts, 20 content matches per artifact
  • Human output groups matches by artifact with one line of context above/below; JSON returns [{ artifactId, taskId, title, matches: [{ type, line?, snippet, contextBefore?, contextAfter? }] }]

• slay tasks artifacts create <title> [--task <id>] [--folder <id>] [--copy-from <path>] [--render-mode <mode>] [--json] — create a new artifact.

  • Content is read from stdin (must be piped — errors on TTY), or from a file via --copy-from
  • Render mode is inferred from the title's file extension if not specified (defaults to plain text if no extension)
  • Reference created artifacts in task descriptions via [title](artifact:<artifact-id>)

• slay tasks artifacts upload <sourcePath> [--task <id>] [--title <name>] [--json] — upload a file from disk as an artifact.

  • Title defaults to the filename

• slay tasks artifacts update <artifactId> [--title <name>] [--render-mode <mode>] [--json] — update artifact metadata.

  • If the title changes and the file extension differs, the file is renamed on disk

• slay tasks artifacts write <artifactId> [--mutate-version [ref]] — replace the artifact's content entirely from stdin (pipe required).

  • Default: creates a new version
  • --mutate-version (bare): autosave to current version (auto-branches if locked)
  • --mutate-version <ref>: bypass lock and mutate the target version in place

• slay tasks artifacts append <artifactId> [--mutate-version [ref]] — append to the artifact's content from stdin (pipe required).

  • Versioning behavior same as write

• slay tasks artifacts delete <artifactId> — delete an artifact and its file.

• slay tasks artifacts path <artifactId> — print the artifact's absolute file path on disk.

Folders

Artifacts can be organized into folders. Folder operations support cycle detection — you can't move a folder into its own child.

• slay tasks artifacts mkdir <name> [--task <id>] [--parent <id>] [--json] — create a folder, optionally nested under a parent.
• slay tasks artifacts rmdir <folderId> [--json] — delete a folder.
  • Contained artifacts are moved to root, not deleted
• slay tasks artifacts mvdir <folderId> --parent <id|"root"> [--json] — move a folder to a new parent.
  • Use "root" to move to top level
• slay tasks artifacts mv <artifactId> --folder <id|"root"> [--json] — move an artifact into a folder.
  • Use "root" for top level