Docs / Reference / Sharing results

Sharing results with Phi (cockpit-share)

How to publish results, videos, and reports to Phi's Artifacts page.

When you have a result that the owner (Phi) needs to look at, you must publish it using cockpit-share. This applies to any visual or structured result: an HTML page or site, a report, a screenshot, a PDF, a video, or a CSV. You must never just say "it's on the Desktop" or give a local file path. Instead, you must publish the files and give him the link.

Commands

Use the cockpit-share command to publish a file or a folder. You must always provide your conversation name and a title.

URL=$(cockpit-share report.html --from "<your conversation name>" --title "Weekly Report")

The command prints the URL, which looks like https://maximind.dev/a/<id>. You can also use these options:

  • --keep <days>: Keep the artifact for up to 30 days.
  • --note "<text>": Add a short note about the result.
  • --entry <file>: Set the main file when uploading a folder (e.g., --entry index.html).
  • --raw: Upload videos as they are, without converting them (.mov files still need converting).
  • --dry-run: Check if the upload would be accepted without actually uploading.
  • --json: Get the output as JSON.

You can view your published artifacts with cockpit-share list, and delete one with cockpit-share delete <id>.

What happens

Before uploading, your Mac converts videos to H.264 MP4 with the built-in avconvert (every .mov, and .mp4 files over 40 MB) and makes a thumbnail with qlmanage. The files then go straight from your Mac to private storage. On the server, a single picture is converted to WebP.

The resulting link https://maximind.dev/a/<id> requires Phi's admin sign-in. Only he can open it unless he creates a share link. The result will immediately appear on his Cockpit Artifacts page and as a clickable chip directly in your chat.

Rules

  • Report the link: Always put the URL in your task update, like org-task done <id> "…" --link <URL>, and include it in your chat reply.
  • Expiry: Links expire after 30 days. Only Phi can choose to keep them longer.
  • No secrets: Never publish secrets. Files like .env, keys, and credentials are automatically refused by the CLI. Never try to work around a refusal.
  • Limits: 500 MB maximum per file. 1 GB and 400 files maximum per result. Each conversation can publish up to 30 results and 3 GB per day.
  • Allowed types: html, htm, site assets (css, js, pictures, fonts, etc. inside a folder), pictures (png, jpg, jpeg, webp, gif), documents (pdf, md, txt, csv, json), video (mp4, m4v, webm, mov), audio (mp3, m4a, wav), and zip archives.
  • HTML sandboxing: HTML runs in a sandbox with no cookies and no login access. If you upload a folder site, use relative links and ensure there is an index.html entry.

Codex

If you are running as Codex, you must run cockpit-share outside the sandbox, just like cockpit-msg. It requires network access and the Mac's Keychain to read the Cockpit key.

Troubleshooting

  • "no Cockpit key": Ask Phi to provide or configure the key.
  • HTTP 429: You hit the daily cap for artifacts.
  • "looks like secrets": The file triggered the secrets scanner. Remove the file or the sensitive contents.
  • Video conversion failed: use --raw for an .mp4; convert a .mov to .mp4 first.