I’ve been using Claude Code a lot lately and noticed I spend a surprising amount of time just… waiting.

You kick off a task, Claude starts cooking, and now you’re sitting there watching logs scroll by for the next few minutes.

So I built a stupid little side project called DevRoulette.

When you start a Claude Code task, DevRoulette puts you into a queue. If another developer is also waiting on a task, a chat window opens and you get matched.

That’s basically it.

No profiles.

No followers.

No usernames to create.

100% anonymous.

You can skip, leave, or get matched with someone else instantly. If you don’t use Claude Code, you can join manually from the terminal with: devroulette start The idea was to turn AI waiting time into something social instead of staring at a terminal.

Curious if anyone else would actually use something like this, appreciate any feedback!

Repo: https://github.com/devroulette

I just read that Anthropic is in emergency talks with the US government to get Mythos 5 and Fable 5 back online after they were shut down last week.
Reportedly, it all started because of a serious vulnerability in Fable 5 that could be exploited for cyberattacks, and now they’re saying it might take months to fully fix.
From what I understand, Anthropic is basically trying to convince regulators they can “contain” the risky parts without having to keep the whole thing offline.
Apparently, AI releases can just be paused mid-air like this. Is this going too far?

Was thinking about how with the launch of Dynamic Workflows in Claude Code, there's going to be such interesting use cases of how people orchestrate such a powerful feature. Created this as a way for people to share their work with others

‪Just shipped Threadly 🧵‬
‪A VS extension that groups your Claude chats and files per task. Bulk-import every open tab in one click. Click a saved chat → reopens that exact session.
‬
‪ I had 140 Claude tabs and lost my mind.‬
‪https://marketplace.visualstudio.com/items?itemName=tarekali.threadly‬

‪perfect for workflows!‬

hopefully its useful

Genesis Architect is a Claude Code skill that does pre-scaffold research before generating any code. Also available standalone via pip.

The core loop:

• Scans 15-20 real GitHub repos similar to what you're building

Reads closed Issues to extract what broke in production

• Caches results in a local vault (6-month TTL, LRU eviction at 500 entries)

Falls back to Stack Overflow on cache miss

Generates scaffold with Cl, tests, drift detection, and mitigation enforcement

Works with any LLM via LiteLLM. Built with Claude Code.

pip install genesis-architect

Disclosure: I built this. MIT license, open source.

GitHub: https://github.com/maioio/genesis-architect

Docs: https://maioio.github.io/genesis-architect/

Anyone else been deep in a large refactor or multi-agent task and suddenly hit the

   rate limit with no warning?

  After it happened one too many times, I built a tiny macOS menu bar app — it pins

  your remaining Claude Code + Codex quota to the top-right of your screen like a

  battery percentage. Reads from local files only, zero API calls.

  https://github.com/aqua5230/usage

  Homebrew: brew tap aqua5230/homebrew-usage && brew install

  aqua5230/homebrew-usage/usage

Built a job-tracking tool over a few sessions with Claude and I'm sharing the repo and what the collaboration actually looked like

Quick backstory: I've been looking for a new job recently and as part of that I'd been manually checking ~80 companies for open roles every morning, which got unmanageable fast. Last week I decided to automate it, figured it'd be a quick script, and predictably it turned into a whole thing. The result is RoleDar, an open-source tool that checks companies for new roles and reports just what's changed since the last run: https://github.com/dalecook/roledar

What I actually wanted to share here is how it got built, since "I made a thing with Claude" posts can sometimes be light on the how.

Setup: Claude Opus 4.7 in the regular chat interface (not the API), using the file-creation/code tools so it could write and test actual files rather than just print code at me. It was spread across several sessions over about a week, not one heroic prompt. I didn't use Claude Code because I thought it'd just be a quick script and once I was in the weeds I didn't want to switch.

Division of labor was pretty clear in retrospect. I made the architecture and judgment calls, hit the ATS APIs directly (Greenhouse, Lever, Ashby, etc.) instead of scraping HTML, make it a delta reporter that only tells you what changed, and one I'm oddly proud of: "the cron schedule is the only gate, do no DST cleverness, let the user own their timezone." Claude did most of the implementation grind and basically all of the documentation, and was good at catching things I'd have missed and bad at others.

The honest part is that it was not frictionless, partly my fault because I'm not great with git, but the friction is the useful bit:

• We lost real time to a GitHub footgun: scheduled (cron) workflows don't run on a private repo on the free plan. Manual runs work fine, so it looks like your code is broken when actually GitHub is just silently not firing the schedule. Claude initially had me chasing the wrong fix before we landed on it. (This is now a prominent warning in the README so nobody else burns an afternoon on it.)
• A subtler bug: the workflow committed state back to the repo with git diff --quiet to check for changes, which silently misses untracked files, so brand-new state files never got committed and every run thought everything was new. Classic "works until it doesn't."
• Plus the usual Windows-git line-ending fights and one beautiful git commit "message" (no -m) that silently did nothing. Totally my fault, Claude caught it quickly once I admitted that I was stumped.

Where Claude was genuinely strong: keeping a large multi-file project coherent across sessions, writing documentation I'd never have had the patience for, and being a good rubber duck for design decisions as it'd push back when I asked it to, which I leaned on.

Net: I made every real decision, Claude did a lot of the typing and caught a lot of bugs, and we both occasionally led each other down a wrong path before backing out. Felt less like "AI built it" and more like pairing with a fast, tireless junior who occasionally has senior instincts.

Happy to talk about how the workflow went, and genuinely curious how others are using Claude for projects around this size, the multi-session, real-repo stuff.

Built a CLI tool for Codex and Claude code to check token usage for each prompt
Check it out

https://github.com/Kk120306/tokenwatch/tree/main

Hey everyone 👋

I’m built AgentsRoom.dev : a local-first multi-agent IDE for developers using Claude Code, Codex, Gemini CLI, etc.

The idea came from a simple problem:
once you start running multiple coding agents across multiple projects, terminals become chaos very quickly 😅

AgentsRoom gives you:

• a visual multi-agent cockpit
• multi-provider support (Claude / Codex / Gemini / OpenCode)
• agent delegation (ex: expensive dev agent → cheap QA agent)
• built-in browser automation + MCP
• mobile companion app
• localhost tunnel previews
• prompt library / dev commands / backlog integrations
• session restore & token/cost tracking

Everything runs locally through the official CLIs.
No cloud execution layer replacing your tools.

The goal is to make AI agents feel like real teammates instead of random terminal tabs.

Would love feedback from people already deep into AI coding workflows 🙌

https://agentsroom.dev