cd /news/ai-policy/dev · home topics ai-policy article
[ARTICLE · art-112418] src=promptcube3.com ↗ pub= topic=ai-policy verified=true sentiment=· neutral

Dev.

Dev.to's new AI disclosure feature fails to render in RSS feeds, as the `{% embed %}` tag is passed through as literal text in the description field, preventing readers from seeing the AI-assist label. The issue affects all tested RSS parsers, while other embed types like Twitter and YouTube render correctly, and a partial workaround exists via the article's HTML endpoint.

read2 min views1 publishedAug 26, 2026
Dev.
Image: Promptcube3 (auto-discovered)

Here's what I'm seeing in the raw RSS output:

<description>
  Excited to see how this feature rolls out and evolves over time
  {% embed https://dev.to/devteam/introducing-ai-disclosure-on-dev-tools-for-nuance-clarity-and-better-feeds-34mk minimal %}
</description>

The {% embed %}

tag isn't being processed at all — it's being passed through as literal text. Most feed readers either ignore it or display it as ugly raw markup. I tried a few different parsers (rss-parser, feedparser, even a manual curl to the RSS endpoint) and they all behave the same way.

My suspicion is that Dev.to is rendering these embeds server-side for the web version but not applying the same processing pipeline to RSS output. That's a pretty common oversight when rolling out new content features, but it's worth flagging because it defeats the whole purpose of the disclosure — if readers never actually see the label, it doesn't help with transparency.

I did a quick test with a few other embed types (Twitter oEmbed, YouTube, etc.) and they seem to render fine in feeds, so it's specifically the {% embed %}

liquid-style tag that's the problem. Either they need to resolve those embeds before generating the RSS XML, or provide a plain-text fallback that includes the disclosure info directly.

Has anyone else run into this? Or better yet, found a workaround? I'd rather not have to manually scrape the article content and re-parse it just to get disclosure status. Also curious if this is intentional — maybe they're treating RSS as a degraded experience on purpose?

Update — Found a partial workaround #

For anyone else hitting this, the article's HTML endpoint does include the disclosure in a <div class="disclosure">

wrapper, so you can at least detect whether a given post has been labeled as AI-assisted. Not ideal, but it's something if you're building tooling around this.

Next Bolting AI onto legacy systems is creating a massive →

these AI tool field notes, with plenty of directly applicable cases.

All Replies (3) #

/api/articles

endpoint — the ai_text

field stays but the disclosure HTML is gone. Could break aggregator filtering.

── more in #ai-policy 4 stories · sorted by recency
── more on @dev.to 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/dev] indexed:0 read:2min 2026-08-26 ·