HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
kunchenguid
firstmate
Shell2026–2026
kunchenguid / firstmate

firstmate

Talk to one agent. Ship with a crew.

6Distinct people
7Mentions
0Explicit recommenders
8.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Talk to one agent. Ship with a crew.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week7 dated mentions

Observed mentions: 2026-07-29 17:41:35 UTC to 2026-10-29 17:01:54 UTC. Weeks start Monday, UTC.

01232026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsJul 272026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-24 00:00:00 UTC to 2026-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-31 00:00:00 UTC to 2026-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-07 00:00:00 UTC to 2026-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 72026-09-14 00:00:00 UTC to 2026-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-21 00:00:00 UTC to 2026-09-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-28 00:00:00 UTC to 2026-10-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-05 00:00:00 UTC to 2026-10-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-12 00:00:00 UTC to 2026-10-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-19 00:00:00 UTC to 2026-10-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-26 00:00:00 UTC to 2026-11-02 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsOct 26

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC312
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC312
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC000
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC000
Aug 242026-08-24 00:00:00 UTC2026-08-31 00:00:00 UTC000
Aug 312026-08-31 00:00:00 UTC2026-09-07 00:00:00 UTC000
Sep 72026-09-07 00:00:00 UTC2026-09-14 00:00:00 UTC000
Sep 142026-09-14 00:00:00 UTC2026-09-21 00:00:00 UTC000
Sep 212026-09-21 00:00:00 UTC2026-09-28 00:00:00 UTC000
Sep 282026-09-28 00:00:00 UTC2026-10-05 00:00:00 UTC000
Oct 52026-10-05 00:00:00 UTC2026-10-12 00:00:00 UTC000
Oct 122026-10-12 00:00:00 UTC2026-10-19 00:00:00 UTC000
Oct 192026-10-19 00:00:00 UTC2026-10-26 00:00:00 UTC000
Oct 262026-10-26 00:00:00 UTC2026-11-02 00:00:00 UTC110

What Hacker News says

7 sources
shiz92·Oct 29, 2026Submission

Ask HN: Agent swarm, orchestra, sequential, what's your workflow?

Hi, Something I've read here and there is people using LLMs for multi-agent orchestration, and I cannot fully understand the idea behind it. So for those of you who do, do you not review code anymore, as you're undoubtedly the bottleneck in this setup? How does this not end up in a chinese whisper game, especially considering how much LLMs infer, guess, and find edge cases and whatnot everywhere? I have two co worker, one is closer to my workflow, plans a lot, build one at a time, almost a duet with our company's LLM. Another one will take the conf room and voice mode over with his orchestrator, define all kind of things and full send it. One is a system engineer the other a web dev, but you get the idea. I have looked at various attempt from people on github to implement these things, eg https://github.com/kunchenguid/firstmate; herdr it
Read the rest
self; claude multi agent process. It has never worked out on my end, is it because of the complexity of the work or am I incompetent at delegating? I understand the importance of mastering LLMs in this brave new world but to me it seems complicated to handle more than one at a time, especially if the problem is complex and requires reading/back and forth with it. I'd appreciate resources of any kind to look deeper into it, or reading some of your work flows, good people of HN. Cheers :)
3 points · Open discussion
This sounds like a mashup of of several things I've been playing with lately... - pi-web (https://pi-web.dev/): a web frontend for the Pi coding harness which can multiplex pi sessions across multiple machines - herdr (https://herdr.dev/): a fairly polished agentic multiplexer TUI, can easily spawn or destroy windows based on subagent activity - firstmate (https://github.com/kunchenguid/firstmate): a meta environment for coding harnesses - more naturally handles spawning and communicating with subagents, managing worktrees, and other SDLC functions, and has a fairly large number of constraints thru bash scripts to ensure better results with less intelligent models
In Superlogical

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.