madarco

Joined 15 years ago

Karma

141

Submissions

Member since

Nov 15

Maker, Developer, Founder - 3DRacers.com

View on Hacker News

Recent submissions

Comment · 1 month ago

I've done the same but using Notion, and I've found really interesting to let the agents write a small "Dev Blog" post on a Notion page with what they built in the sessions, with screenshots, videos etc.

Also working with parallel sandboxes is a must: I use a manger session that read/write the issues from Notion and dispatch them to workers, it handles similar work to the same box to minimize merge conflicts.

PS: I'm using AgentBox for this (discl: I'm the author, free OSS): npm -g i @madarco/agentbox but now also Claude is releasing Projects (still rolling out) and Cursor had cloud agents for a while

Show HN: Agentbox – Teleport your repo into sandboxes with no worktree juggling github.com

4 madarco 1 month ago 0 comments

Comment · 3 months ago

nono is great but you'll still won't be able to run multiple dev servers, dbs or test in the browser...

the better alternative is using sandboxes, for TRUE isolation.

but most people skip them because it's harder to set up a dev environment in a sandbox, for this I built agentbox [1], a tool to teleport your files, skills, settings, claude/codex subscriptions etc in any of the popular sandboxes. eg:

agentbox e2b claude

or:

agentbox hetzner codex

each session is persistent, with a full VM, with a browser, webVNC screen sharing and local https tunnel for easy preview on *.localhost domains.

Also git credentials never leave your pc: when a box needs access it passes through the agentbox service running on your machine, which allows PR creations, comments but only on the box branch, no deletion etc.

[1] https://github.com/madarco/agentbox

Comment · 4 months ago

It had already been like this long before widespread LLM adoption: quality hiring was only really possible through manual candidate scouting on LinkedIn, at conferences, through word of mouth, and so on.

Sending a CV had already become mostly useless 3–4 years ago because of the huge amount of noise: candidates applying from all over the world, often even spoofing their actual location, FAANGs firing, flooding the market with (in theory) great candidates with great resumes.

The solution is the same one that has been successfully used forever: a trial period.

Luckily, a video interview with a senior developer is still enough to spot a good candidate.

Go through real code: add a bug to a branch of your codebase, have the candidate share their screen on TeamViewer, and let them debug and fix the issue. Ask questions live to understand how they reason about the system, how they would test whether the change works, and so on.

This will filter out 99% of candidates. But it is still possible to get lucky, which is why the trial period matters.

I’ve never had major issues and have always hired very strong engineers. I only had to terminate someone after the trial period twice.

Comment · 4 months ago

with the advent of NEOgeo everything changed, Super Side Kick, Goal Goal Goal and other wonderful games, often with a 4 players cabinet!

Comment · 5 months ago

I do the same, and faced the issue that claude/codex loose context when doing subtasks (and subagent don't have plan mode).

So I've built Agentbox to be able to launch from claude/codex multiple VMs with claude/codex (can also mix). The parent agent watch for prompts and questions, enforce /review, /simplify, that the sub agents file a PR and wait for bugbot comments etc.

This way the parent agent running in a /goal don't loose context, enforce a good workflow, manage the backlog and parallelize/merge back the work on the main repo

https://github.com/madarco/agentbox MIT license

Comment · 5 months ago

you are right, I've experimented with cp -a on macOS as well for https://github.com/madarco/agentbox and in the end found it's actually faster to use worktrees inside docker containers while mounting your .git repo inside them.

Then after the node_modules (or apt packages) are installed, take a docker commit snapshot.

Now I have truly isolated parallel workspaces in <10s.

Also the system was easy to adapt to cloud environments as well so now I have Hetzner, Vercel, Daytona as well (using their native snapshotting systems for fast boot after the initial setup)

Comment · 5 months ago