Skip to main content

Creating multi-artifact packets in Work

Generate multiple artifacts in one chat.

What are multi-artifact packets?

A multi-artifact packet is a collection of related artifacts bundled together into a single deliverable. Instead of creating one artifact per chat and managing them separately, packets let you group multiple artifacts — for example, a slide deck, an accompanying dashboard, and a supporting document — into one cohesive unit.

Packets are useful when a project or deliverable naturally spans multiple formats: you might want a presentation plus a data deep-dive, or a report with a supporting spreadsheet and a one-page summary PDF.

Creating a packet

To create a multi-artifact packet, ask Coworker to produce multiple related outputs in a single Build mode session. For example:

  • "Create a packet for our Q2 pipeline review: a slide deck for the exec presentation, a dashboard with the underlying data, and a one-page PDF summary."

  • "Build a sales enablement packet: a product overview deck and a competitor comparison document."

Coworker will generate each artifact in sequence and group them in the Canvas panel. You'll see all artifacts for the chat accessible via the artifact navigation controls.

Navigating a packet

When a chat has multiple artifacts, you can switch between them using the artifact type tabs or navigation in the Canvas panel. Each artifact can be:

  • Viewed and edited independently

  • Exported in its own format

  • Shared individually or as a group via The Commons

Sharing a packet

You can share individual artifacts from a packet, or share the entire chat (which preserves all artifacts together). When contributing to The Library, you can tag the artifacts together so teammates can find and use the full packet as a template set.

When to use packets vs. single artifacts

Use a single artifact when...

Use a packet when...

You need one deliverable (e.g., a deck for a customer meeting)

A project requires multiple formats (deck + data + summary)

Your audience only needs one view

Different stakeholders need different views of the same information

The output is self-contained

You want to keep related artifacts organized together

Tips

  • Be explicit about what you want in the packet upfront — listing the artifacts you need in your initial prompt gives Coworker clear direction.

  • You can add to an existing packet mid-conversation: "Also create a one-page PDF summary of the deck you just built."

  • Packets created in a single chat session stay grouped together, making it easy to find and share the full set.

Did this answer your question?