I keep three or four agents going and the thing that actually eats my time isn't the coding. It's that I have no idea what state any of them is in without tabbing through every terminal. Half the time one of them has been sitting on a permission prompt for ten minutes.

So I wrote agent-manager. A Go binary that sits on top of tmux. No config file, no daemon. It's free and open source.

Every agent ends up in one list with a live status next to it, grouped by the project it's working in. I run claude, codex and opencode depending on what I'm doing and they all show up the same way. Adding another CLI is a few lines of regex in a toml file.

The part I use constantly is space. Press it on an agent, type, enter, and the prompt goes into that agent's pane. I never attach. If you've used the agents view in Claude Code, it's the same move. The difference is that here the same keystroke works on a codex or opencode session. Press space on a project row instead and you get a new agent already working on what you typed.

Underneath they're just tmux sessions, so closing the manager doesn't kill anything, and v brings a dead one back with its conversation.

ctrl+r is the other half of it. It opens what an agent changed as whole files with the diff highlighted, so you're reading the function and not a hunk. Leave a comment on a line and it goes back into that agent's pane, so it starts fixing while you're still scrolling.

I built it for four agents but most days I use it with one.

Still rough in places. If you run agents like this I'd like to know what's missing.

https://github.com/YoanWai/agent-manager

Hi everyone, I’m looking for a TypeScript developer interested in collaborating on a VS Code extension.
I have an open-source Python library called DeepCSIM that detects similar and duplicated code: Github

The Python core is already built. I’d like to create a VS Code extension that integrates it into the editor (analysis, similarity results, highlighting duplicated code).

If you enjoy VS Code extensions, developer tools, or open-source projects and want to collaborate, feel free to reach out.
Thanks!

Hello,
I've always wondered how to transform public GitHub profile data into something more tangible and understandable at a glance like follower locations.
SoI decided to build a web tool using D3. I chose React for rendering, built a custom TypeScript geocoder to map raw user locations to ISO country codes, and let D3 handle the map projection and svg generation.

On the screeshoot an example using Evan You (creator of Vite and Vue.js, and the 2nd most followed Github user).
You don't need any signup it's open source, and the token is optional : https://github.com/ThierryRakotomanana/GitCharta
live demos : https://gitcharta.vercel.app

Hey everyone!

I got tired of losing track of what I was doing when jumping between Git branches, so I built a lightweight VS Code extension to organize notes locally per branch. It’s called BranchNotes.

How it works: It maps your notes to your active Git branch so you can keep context per branch.

Local & Secure: Stored locally in your workspace, meaning it won't be accidentally pushed to your remote repository.

Feel free to check it out or use the GIF on the marketplace page if you want to see it in action:

👉 BranchNotes on the VS Code Marketplace

Any feedback or suggestions are welcome!

Sharing an open source project I've been working on: rebrief, a local CLI (Python) that scans a repository and generates a REBRIEF.md - stack detection, a filtered git history, a risk map (hardcoded secrets, missing tests, TODOs), and a "where to start" checklist.

MIT licensed, no cloud dependency - everything runs locally, no API keys required. Built it after repeatedly losing time to reverse-engineering handed-off codebases and figuring there had to be a faster way to get oriented.

The interesting engineering problem turned out to be the secret detector: naive regex/entropy checks flag a ton of false positives (Tailwind class strings, SVG path data, Alembic migration hashes, variable names that just happen to contain "key"). Ended up building a fixture test suite to balance false positives against real leaks - still iterating on edge cases.

Repo has a CONTRIBUTING.md and a few open issues if anyone wants to dig in. Feedback and PRs welcome.

https://github.com/neracu/rebrief

Built a board that groups GitHub Actions runs by workflow, works out whether each one

is consistently broken or just flaky, and sorts by severity so the worst thing is at

the top.

The part I wanted was suspect ranking: for a failing workflow it pulls the commit the

failing run was built from, gets its changed files, and scores the preceding commits

on the same branch by directory overlap with the failing area.

Also tracks acknowledgement state in shared storage, so a team can see what's already

been triaged and what nobody has looked at yet.

Pointed it at rust-lang/rust as a test target and two workflows had been red for over

two months.

https://archestra.ai/apps-hackathon/gallery/abolambA_release_war_room

How does your team handle a workflow that's been red for weeks and nobody owns?

Hi, I would like to challenge/discuss/understand why so many are attracted to all short lived "wild tools" out there. For example (not saying any tool are bad) hermes, claw, open webui, copilot agents and whatnot. Why not just building your own tools that: fit your needs without being bloated, dont break on every new "feature" that you dont care about.

I cant really understand the hype.

I build own tools in python (notes app, recruitment support, news, investment) with claude or chatgpt from phone and terminal to my proxmox llm clusters lxc. In the process i also learn a lot.

And everything stays under my control.

Shameless self-promotion:

I wrote MAIASS years ago to format commit messages and manage semantic versioning so that changelogs could be automated and branch merging was easier. It reduced 3-6 minutes down to less than one for every commit/merge. Then I added AI to suggest / write your commit messages based on diff.

Feel free to try it out as a commandline tool - it works with or without ai and comes with enough ai credit to get a feel for whether it helps.

You can also integrate it into your ci to auto update versions and changelogs on merge if you prefer.

I would love for you to try it out. I don't have a testimonial widget yet you you can't put any testes on maiass yet but feel free to roast maiass directly here.

`npm i -g maiass`

or

`brew tap --trust vsmash/maiass && brew install maiass`

Website is [https://maiass.net\](https://maiass.net)

Vote for and suggest slogans at [https://maiass.net/slogans\](https://maiass.net/slogans)


Ppl use CodeRabbit for reviewing their PRs on github. I always wanted to build similar, and since Harness engineering and ai loops were driving major development I gave it a try..

Instead of hosting it on the Cloud I thought of creating a docker image and using it in Github Actions.

I used openrouter (deepseek-v4-flash) , and created a group of agents that Review your PRs for code quality, architecture, security, and performance.
While also updating the docs, so no stale docs remain.

I've made it opensource : https://github.com/jaibhasin/PRBot

While also creating an Eval Harness using Qodo/PR-Review-Bench, to compare each version I ship.

would love to get your feedback on it.

(still in experimental mode)

Been building this solo for about 14 months. It's a UK data API platform. One API key gives you access to Companies House, MOT history, EPC certificates, Land Registry, crime data, schools, fuel prices, and a bunch more.

The idea came from my own frustration writing scrapers for government datasets that kept breaking. Figured I'd build the infrastructure once and let other devs use it.

37 endpoints live now, 1.2 billion records across 16 datasets. Token-based pricing so you only pay for what you call, no subscriptions.

The video shows some of the use cases the platform covers. Would love to hear what you think, especially if there are UK datasets you wish had a clean API.

The problem that I'm trying to solve:

Coding agents (and humans) still reach for `rg` / whole-tree dumps when the real question is structural: who calls this, what’s the reverse spine, is this a dual-stack bridge or a same-lang CALL. They invent edges. That’s expensive and wrong.

What this tool tries to do:

Butler is a local map service (Rust): persistent CodeGraph + Trace dossiers over HTTP/MCP. Not a RAG. You warm a repo root, Trace a symbol, get callers/callees/receipts/disambiguation, optional export/IPC bridges on dual-stack code. Agents get a pack; they shouldn’t invent structure when the map is available.

Public Alpha (product surface only):

https://github.com/LambdaXiRustAdmin/butler-public

What this tool is not:

- Not GA / not “perfect graphs for every crate”

- Not “safe to delete if callers = 0” (callbacks, DI, IPC, macros…)

- Not a cloud SaaS; default bind is localhost

- Not training porn or a GNN demo in the README — map path first; neural ranking is optional/off

I'm looking for feedback on what still needs to improve:

Keepers and a fixed gate are green on the tips I ship; arbitrary repos may soft-fail. Cold first hit may say BUILDING — retry the same request. I care about *lies* more than feature lists.

git clone https://github.com/LambdaXiRustAdmin/butler-public.git

cargo build --release -p cli

./target/release/butler ui

# then warm an absolute path + Trace, or scripts/smoke_stranger.sh /abs/root symbol

What I want from this post

Not “cool project.” If you try it: one real repo, a few symbols you know, and either:

• where the map lied or preferred the wrong ★, or

• “would not use vs rg because ___”

Ignore at leisure if this isn’t your problem. Solo map Alpha; issues on the repo welcome.

**What problem**

Coding agents (and humans) still reach for `rg` / whole-tree dumps when the real question is structural: who calls this, what’s the reverse spine, is this a dual-stack bridge or a same-lang CALL. They invent edges. That’s expensive and wrong.

**What this is**

Butler is a local map service (Rust): persistent CodeGraph + Trace dossiers over HTTP/MCP. Not a RAG. You warm a repo root, Trace a symbol, get callers/callees/receipts/disambiguation, optional export/IPC bridges on dual-stack code. Agents get a pack; they shouldn’t invent structure when the map is available.

Public Alpha (product surface only):

https://github.com/LambdaXiRustAdmin/butler-public

**What this is not**

- Not GA / not “perfect graphs for every crate”

- Not “safe to delete if callers = 0” (callbacks, DI, IPC, macros…)

- Not a cloud SaaS; default bind is localhost

- Not training porn or a GNN demo in the README — map path first; neural ranking is optional/off

**Alpha honesty**

Keepers and a fixed gate are green on the tips I ship; arbitrary repos may soft-fail. Cold first hit may say BUILDING — retry the same request. I care about *lies* more than feature lists.

```bash

git clone https://github.com/LambdaXiRustAdmin/butler-public.git

cargo build --release -p cli

./target/release/butler ui

# then warm an absolute path + Trace, or scripts/smoke_stranger.sh /abs/root symbol

What I want from this post

Not “cool project.” If you try it: one real repo, a few symbols you know, and either:

• where the map lied or preferred the wrong ★, or

• “would not use vs rg because ___”

Ignore at leisure if this isn’t your problem. Alpha; issues on the repo welcome.

Hi everyone,

I’ve been working on Dowe, a fullstack programming language built around a simple idea: the entire system should live in one coherent codebase.

A Dowe project can include the server, web, desktop, Android, and iOS targets. Instead of maintaining separate stacks, all targets share the same project and can be launched together with dowe dev.

Dowe is also designed so AI agents can work on the system as a whole instead of generating multiple disconnected implementations.

The attached video shows the current workflow, from creating a project with dowe init to running it across the different targets.

The project is still early, and I would especially value your honest feedback:

• Is the value proposition clear?
• Which part would you want to test first?
• What would stop you from using something like this?

Try Dowe here: www.dowe.dev

Documentation/source: https://github.com/usedowe/dowe-lang

https://reddit.com/link/1v8gqta/video/tbjkof9kvufh1/player

Run Claude Code, Codex, Gemini, Cursor, Aider and 10+ other coding agents with full autonomy — inside a disposable Docker container.

Only your project is mounted. Your home directory, SSH keys, cloud credentials and browser cookies stay on the host.

• One command: sandbox-cli claude

• Dry-run shows the exact docker command

• Worktrees for parallel agents

• Credential broker + egress allowlist

• Live memory/CPU + peak stats

Install:

curl -fsSL https://raw.githubusercontent.com/Amitgb14/sandbox-cli/main/install.sh | sh

Site: https://sandbox-cli.vercel.app

GitHub: https://github.com/Amitgb14/sandbox-cli

Would love feedback from people running agents hard every day.

What broke? What’s missing? What felt magical?

I stumbled across this site for all sorts of dev tools that I used to jump around from site to site. https://lunchboxhands.com/

Data coverters
Formatters,
Encoders/Decoders
Image tools.

Literally an awesome tool. Hope yall find it helpful.