WeSearch

I built an open protocol to make AI coding agents follow senior-engineering workflows

·2 min read · 0 reactions · 0 comments · 34 views
I built an open protocol to make AI coding agents follow senior-engineering workflows
TL;DR · WeSearch summary

Sabir Semerkant has developed an open protocol called The Polyglot Protocol to enhance AI coding agents' adherence to senior-engineering workflows. This protocol addresses common issues faced by AI agents, such as skipping repository discovery and ignoring project conventions. It is designed to be model-agnostic and aims to provide a practical framework for developers to adapt and improve upon.

Key facts
How this story was covered

2 outlets in our directory ran this story, first to last over 2 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 1
About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

Original article
DEV.to (Top)
Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherDEV.to (Top)
Canonical URLhttps://dev.to/sabir_semerkant/i-built-an-open-protocol-to-make-ai-coding-agents-follow-senior-engineering-workflows-11ep
Publication timeSun, 24 May 2026 00:11:31 +0000
Retrieval time2026-05-24T00:37:28.644Z
Last seen2026-05-24T00:37:28.644Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterTn2G20VmjzVL · 2 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3948368) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Sabir Semerkant Posted on May 24 I built an open protocol to make AI coding agents follow senior-engineering workflows #opensource #ai #devtools #programming AI coding agents are getting better fast, but I kept running into the same failure modes: they skip repository discovery they invent APIs, flags, or config keys they ignore existing project conventions they add unnecessary infrastructure they skip validation they treat unsupported checks as silently done they finish without a…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)