To me, nostr feels more like a group chat than "social media"
Justin Moon
npub1zxu6...cx2y
ooooooöøōoooòö yea 

Made a CLI that can query GPT5 Pro. In my experience that's the smartest model. Very convenient to use as an "oracle" when coding agents like Sonnet 4.5 get stuck or need guidance. 
GitHub
GitHub - justinmoon/gpt5-pro
Contribute to justinmoon/gpt5-pro development by creating an account on GitHub.
Everyone thought lightning was going to be a client protocol, but it turned out to be a server protocol.
Something similar might be true for nostr ...
I started writing a TUI coding agent last week and this `/explain` feature is the first one that's really sick. Gives you a tutorial about current branch relative to master. Will add many more bells and whistles but this is already amazing.
Finally setup syncthing. I've always hated sysadmin, but the vibability of nix configs has totally changed changed my tune @Gigi
GN 

little tool i made for reviewing coding agent changes
Reviewing AI-Generated Code with `rv`
A simple tool to review all git changes at once when working with coding agents

Has anyone built a Disqus style comments section on nostr?
insanely useful script for vibe-coding guis on a mac. it just focuses and screenshots a window by name. so this allows the agent to see what the gui looks like.


Gist
screenshot-window
GitHub Gist: instantly share code, notes, and snippets.

The more i vibecode and the better i get at it, the less i find github useful. I already have self-hosted runner so don't need their ci. it's move convenient to store issues and roadmap in text files so i don't need issues. Starting to do a local merge pipeline so don't need PRs.
Just saw this neat video which makes me want to stop using the GitHub git server
Might work well with gitworkshop, too (cc @DanConwayDev)

Quickstart - Factory Documentation
Get productive with droid in 5 minutes using the interactive terminal UI.
This is something i vibecoded a few weeks ago. just a static prototype and doesn't work yet, but i keep thinking about it and might actually implement
Idea is that I would define a javascript DSL for coding agent state machines (e.g. "create 4 agents to all implement this task, then launch 2 reviewer, then have the reviewers argue, then choose one branch and make a pr"). maybe it would just be xstate (https://stately.ai/docs/xstate).
User would explain workflow they want in natural languages and a state machine workflow would be generated automatically. they could inspect it -- should be short like 100 LOC or less. Could ask for changes in natural language. They see a nice mermaid style diagram. Then they could launch it and the state machine runtime would orchestrate this workflow.
The state machine templates could be easily shared since they're just short text snippets


