Generated Markdown artifacts cannot be shared with a team like plans

[vikvang]

Summary

Generated Markdown artifacts in Warp do not appear to have a way to be shared with a team as an artifact, unlike plans, which can be exported or shared as links.

Problem

When an agent generates a .md file as an artifact, the artifact can be useful for team collaboration or review. The user expected a share affordance comparable to plan artifacts, but could not find a way to share the Markdown artifact directly with their team.

Expected behavior

Generated Markdown artifacts should expose a team-shareable artifact link or equivalent collaboration affordance, consistent with the way plans can be shared.

Actual behavior

The Markdown artifact is generated, but there does not appear to be a way to share it as an artifact with the team. The apparent workaround is to copy, export, or save the Markdown manually, which loses the artifact-style sharing flow.

Reproduction steps or desired workflow

1. Ask Warp/Oz to generate an .md artifact.
2. Open or view the generated artifact in Warp.
3. Try to share it with a team the same way a plan can be shared.
4. No comparable share affordance is visible.

Artifacts

None attached

Warp version

Unknown

Operating system

macOS

Possible source references

• https://docs.warp.dev/agent-platform/warp-agents/planning#saving-and-sharing: documents that plans can be exported or shared as links, which is the comparable sharing flow the user expected for Markdown artifacts.

[oz-for-oss]

@vikvang

Here's what I found while triaging this issue:

This appears to be a feature gap rather than a local macOS issue. Plans are saved as Warp Drive-backed documents that can be shared, while generated file artifacts currently expose download/view actions only.

Maintainer details

I concluded that generated Markdown/file artifacts currently appear to be downloadable conversation/run artifacts rather than Warp Drive shareable objects, so they do not inherit the plan-sharing flow..

Triage

This looks like a feature request / product gap rather than a macOS-specific bug. Generated file artifacts, including Markdown files, are currently handled as agent artifacts that can be downloaded, while plans are saved as Warp Drive notebooks and therefore get the existing share-link/team collaboration flow.

Evidence

• The public planning docs describe plans as automatically saved in Warp Drive, with options to export as Markdown or share a link.
• app/src/ai/artifacts/buttons.rs renders Artifact::File as a Download file button and only routes plans to Open plan; there is no file-artifact share/copy-link action in the artifact button model.
• Artifact event handlers in app/src/ai/conversation_details_panel.rs, app/src/ai/agent_management/view.rs, and notification rendering all handle file artifacts by calling download_file_artifact.
• app/src/ai/ai_document_view.rs and app/src/notebooks/notebook.rs set a ShareableObject::WarpDriveObject once a plan/notebook has a server sync ID, which is what unlocks the Warp Drive sharing dialog. app/src/drive/sharing/mod.rs currently models shareable Warp Drive objects, sessions, and AI conversations, but not standalone file artifacts.
• The file artifact upload/download path (create_file_artifact_upload_target, confirm_file_artifact_upload, and get_artifact_download) stores artifact metadata and returns an expiring download URL, not a durable team-shareable artifact object/link.

Likely next step

This likely needs product/design direction on whether generated Markdown artifacts should become shareable Warp Drive objects, have their own artifact-share link/ACL model, or offer a shortcut to promote/import Markdown artifacts into a shareable notebook/plan-style document.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz