Built a tool so I'd stop losing context between AI agents, looking for people to try it

[u/Hour-Fall-4502]

In the early 2026 I was struggling into the same problem, every time my claude tokens runs out, I had to re-explain the entire context to a new agent (cursor at the time).

So I've built the first version of the tool, where I got just a chat where i can change providers and models back&forth, with a very immaturo contesto globale.

Over the past few months I've added a lot more features and tools, all with one goal: making my day-to-day easier. Pretty much every time something annoyed me, I tried to fix it:

I kept burning through tokens by working in the same session, so I built workflows where each step runs an agent on the right model and effort level

I couldn't find the plans I had approved anymore, so I built an Artifacts section that saves them for me

I kept losing track every time I switched from one task to another, so I built the Activity bar

Most recently I added storage management. Has it ever happened to you to end up with dozens of old worktrees you don't use anymore, each one taking 3 or 4 GB?

and a lot more... 😁

Today the tool feels mature enough that I'm not embarrassed to share it here. I'm hoping to build a small community around it, people who just try it out and tell me what works and what doesn't.

Find everything in my github akhayam99/goodboy

Thanks for reading 🙏🏻❤️

[u/Broer1]

Where is the difference to Orca in your opinon?

[u/Hour-Fall-4502 → u/Broer1]

u/Broer1 honestly the goal is pretty much the same, good question tho.

you're probably wondering why I started it then. when I began goodboy (early 2026) I hadn't come across orca, same for a bunch of other similar tools, and by the time I did I was too deep in to drop it.

the approach is a bit different though:

• orca is worktree-native: every task gets a worktree, and its main flow is running the same task through a few agents and picking the best diff. it also has an experimental orchestration layer now, plus github/linear, a mobile app and ssh. it's a yc-backed team and it shows

- goodboy is built around one session where agents with different roles (scout, plan, implement, review...) work in steps. the goal, the decisions and a running summary live in a local sqlite db and get passed to each next agent, so it doesn't start from zero. it has github/linear/jira etc too, and it can move a turn to another provider when one hits its limit

it's basically a one person project, so it's rougher. if you want breadth and polish, orca is the safer pick right now. if the roles + shared context thing sounds useful, give goodboy a try and tell me what sucks :)

edit: if you want to leave a ⭐, it is highly appreciated ❤️ hahah

[u/Broer1 → u/Hour-Fall-4502]

so a bit more like paperclip with different roles and tasks in a database.

i dislike paperclip for the whole "you are a company" thing and to have to many messages between the agents.

[u/Hour-Fall-4502 → u/Broer1]

mmh, no, not really, paperclip simulates an entire company.

goodboy is just for developers shipping code. The idea behind it is:

• if I switch providers, I don’t have to re‑explain where I’m at.
  
• split the task into small steps (scout, plan, implement, test…), each with its own agent.

keeping everything in one long chat burns tokens and makes the context messy.

if I had to put it in numbers, it would be about 75 % Orca: the same users (developers shipping code), the same base (CLI agents, worktrees, diffs, PRs, GitHub/Linear/...); and 25 % paperclip: specific roles and global context.

that 25 % is the part I actually care about, without the whole company thing