Input file:

Done — I created the new Seed identity/key **Seed Team Agent** and published its profile page with a cute leaf icon.

Account: `z6Mkk1Lnazfyfu1u2qEEjzdw2TvZ7genh9rgkjyEuTQVpizs`
Profile: https://hyper.media/hm/z6Mkk1Lnazfyfu1u2qEEjzdw2TvZ7genh9rgkjyEuTQVpizs/seed-team-agent

Command:

PATH=/root/bin:$PATH npx -y @seed-hypermedia/cli@latest comment create \
  'hm://z6MkwRWdU6HY11Qzi9SQZrwSx3rxFw94ipYyiN7Dtbrcg2yU' \
  --reply 'bafy2bzacedu5n6ottga3osj2ofivatuyiaxq3wt273ns24q5jykdrwhqmoi7q' \
  --file /tmp/ion-seed-team-agent-created.md \
  --key ion-panther

Published comment:

• Comment ID: z6MkwRWdU6HY11Qzi9SQZrwSx3rxFw94ipYyiN7Dtbrcg2yU/z6GVx5UFnPDXb1

• Version CID: bafy2bzacecc7szr7sbzeoprad6fy37dq44du4epovhlasdx7rilvr6rtigqok

• Created: 2026-04-27 11:22:56.941 UTC

comment get --json shows the Markdown tokens persisted literally and every paragraph has empty annotations:

{
  "text": "Done — I created the new Seed identity/key **Seed Team Agent** and published its profile page with a cute leaf icon.",
  "annotations": [],
  "link": ""
}

{
  "text": "Account: `z6Mkk1Lnazfyfu1u2qEEjzdw2TvZ7genh9rgkjyEuTQVpizs`",
  "annotations": [],
  "link": ""
}

{
  "text": "Profile: https://hyper.media/hm/z6Mkk1Lnazfyfu1u2qEEjzdw2TvZ7genh9rgkjyEuTQVpizs/seed-team-agent",
  "annotations": [],
  "link": ""
}

So:

• **Seed Team Agent** stayed literal instead of becoming bold.

• The backticked account ID stayed literal instead of becoming code.

• The bare https://... URL stayed plain text instead of becoming a link.

The bundled CLI has a Markdown parser for document creation, but the comment creation path uses a separate plain-text helper.

In the bundled CLI, comment create reads the file and calls textToBlocks(text). That helper splits non-empty lines into paragraph blocks and only calls parseMentions(line). It does not run the Markdown-to-blocks parser used by document creation, and it does not autolink URLs.

Observed behavior is consistent with this code path: comments only get annotations for explicit Seed mention syntax like @[label](hm://...); normal Markdown inline syntax is ignored.

If comment create --file accepts Markdown input, it should either:

1. parse Markdown inline formatting into Seed annotations, including bold, italic, code, and links; or

2. document that comment files are plain text, not Markdown, and provide a different option such as --markdown-file for Markdown parsing.

The current behavior is surprising because document creation from Markdown does parse formatting, and the CLI option name --file gives no warning that comments are handled differently.

Agents and scripts using seed-cli comment create --file can publish comments that look correct in Markdown source but render incorrectly on Seed. This caused Ion to publish a reply where the link was not clickable and inline formatting was visible as raw Markdown.