Hey we shipped a new Go code generator for lexicon types. Been in production for a couple weeks now 🥳 Based off of @bnewbold.net's cobalt work and @hypha.coop's go-dasl for DRISL serialization. Copies indigo's echo server stub generation verbatim. 100% compatible with @atproto/lex lockfiles.
GitHub - streamplace/glex: Go code generation for atproto. glex: enter the repo
github.comJul 25, 2026 at 7:13 PM
Rethinking the TypeScript Lexicon tooling - Matthieu's Leaflet
The official Lexicon code generation tooling hasn't evolved much since its initial release. While it serves the core atproto codebase well, third-party developers face significant challenges with bundle size, manual maintenance, and architectural constraints that make building production-ready applications unnecessarily difficult.
typelex – An experimental TypeSpec syntax for Lexicon
An experimental TypeSpec syntax for AT Protocol Lexicons. Write Lexicons in a more readable syntax using TypeSpec.
The Go Programming Language
Go is an open source programming language that makes it simple to build secure, scalable systems.
Lexicon Store - ATProto Lexicon Schema Registry
Discover and explore AT Protocol lexicon schemas. The verified registry for Bluesky and ATProto lexicons.
These 4 Code Snippets won WWDC
WWDC 2025 delivered on the one thing I was hoping to see from WWDC 2024: free, unlimited invocation of Apple's on-device language models by developers. It may…
feeds package - github.com/gorilla/feeds - Go Packages
Syndication (feed) generator library for golang.
Lex make a registry - Sri's leaflets
Introducing lexicon.store - an unconventional ATProto Lexicon Registry
standard.site/lexicons
Shared lexicon schemas for long-form publishing on AT Protocol. Uses typescript to json via prototypey.
a few people found this tool I made a while ago useful in @alex.bsky.team's lexicon workshop yesterday at #atmosphereconf, so resharing here for anyone else who wants to write their lexicons in typescript prototypey.org
New Build Notes article discussing ATProto and how we as developers can go about forming standard lexicons for common datatypes without being overly prescriptive on implementation details that would limit creativity and competition blog.stygiantech.dev/a/3msmoumcr4d23-atproto-stand…
ATProto Standards Bodies—Guiding the Future of the Network
blog.stygiantech.dev#atproto is there anything we can do to solve the issues plaguing the lexicon specification right now I don't think it's good that the reference TS and Go SDK do not agree with each other on how lexicons should be interpreted
Ricardo J. Méndez
Hmm. That's generated with prototypey and goat lex lint didn't complain, but I'll look into it, thanks.
we're officially moving to production lexicons `fm.teal.feed.play`, etc. i'm also filing PRs to multiple repos right now to help with the move, so look for those in your inbox (i'll also ping on bsky) the lexicons will be published to the @teal.fm repo here soon
