Can OmO Support Trace Commons?

[TomLucidor]

Sometimes the conversation can be turned into a dataset for people to share. I wonder if OmO can dump every single subagent to have it go up there https://trace-commons-web.hf.space/

[starkmarkus]

This sounds like a useful idea, especially if OmO already has structured traces for subagent runs.

From the Trace Commons page, it looks like the intended workflow is not just “dump everything”, but: export a coding-agent session, anonymize it locally, show the user what was removed, and only submit after explicit confirmation. It also seems limited to public open-source repositories, which is important.

So I think OmO support would make sense, but I would design it as an explicit export/donation flow rather than automatic uploading.

The useful shape could be something like:

• export each subagent trace in a common JSON format
• include parent/child relationships between the main agent and subagents
• include prompts, tool calls, file edits, command outputs, and final diffs where available
• redact paths, usernames, tokens, secrets, private URLs, and environment-specific data locally
• show a preview/diff of what will be shared
• require explicit user confirmation before upload
• block or warn for private/proprietary repositories

That would make OmO traces much more useful for research while keeping the privacy boundary clear.

So my answer would be: yes, this seems like a reasonable feature request, but I would not phrase it as “dump every single subagent” by default. I would phrase it as “export/donate anonymized subagent traces to Trace Commons with local review and opt-in upload.”

[UnknownHawkins]

Maybe include a code block showing command to install skill and run donation.

We need 2-4 short paragraphs max. Could be 2 paragraphs.

Let's produce:

Paragraph 1: Yes, OmO can push