Questions you are probably asking

No. They are educational experiments built for this project, the website and the accompanying video. They are not official Convex SDKs, not published packages, and they will not be maintained or supported going forward. For real work, use the official Convex client libraries.

The core client surface: queries, mutations, actions, JSON-safe values, auth-token forwarding and error handling, plus realtime query subscriptions over WebSockets for the Live badge. They do not cover the full official SDK surface.

No, client-side only. The backend the clients talk to is a normal Convex backend with its queries, mutations and actions written in TypeScript as usual. This project is about calling into a Convex backend from each language, the way a frontend or another service would. So no, sadly there is no COBOL running on Convex's servers.

Yes, all of it. The human job was direction: picking the goals, setting the rules, reviewing the evidence and deciding what happened next. The agents did the typing, and the test suite kept everyone honest.

Every badge comes from ./run verify-all at an exact clean commit: 31 of 31 conformance checks against a local backend and 31 of 31 against a real hosted deployment over TLS. The evidence behind every badge, including the commit, container digest, toolchain and timestamp, is on this site for every language.

Install Docker, clone the repository, and run ./run verify-example <language> from the repository root. That builds the language's pinned toolchain in Docker and runs its canonical example against a real backend, so nothing needs to be installed on your machine except Docker itself.

Infeasible languages were recorded with evidence in the graveyard and replaced from the roster reserve list, so the roster still reaches 100. Nothing was quietly dropped.

Maybe! If enough people want a fuller implementation of a particular language, it could happen. Say so in the video comments.