Back to browse
GitHub Repository

Agent harness orchestration

2 starsJavaScript

BeeZee – OSS lightweight remote harness orchestration and observability

by PAndreew·May 27, 2026·1 point·0 comments

AI Analysis

MidShip ItNiche Gem

Token tracking across harnesses is useful, but orchestration space is already crowded.

Strengths
  • Token consumption visibility across multiple harnesses addresses a real blind spot
  • Tailscale integration for remote access without manual SSH navigation
  • Unified session management lets you resume Claude Code threads in Codex
Weaknesses
  • 3-day-old repo with 0 stars, 0 forks, and admitted 99% LLM-written code
  • Paid cloud relay competes with free alternatives without clear differentiation
Target Audience

Developers managing multiple AI coding agents across devices

Similar To

Continue · Cursor · LangFlow

Post Description

Edit: link seems to be broken - https://github.com/BeeZeeAgent/beezee

First I'd like to address the concerns that might naturally come up.

This repo is 3 days old, yet another LLM slop!

Yes, that's partly true. The reason behind it's age is that I ported it to its dedicated Github account. I had slight variations of the same SW in my personal repo since the end of February. I just wanted to be very clear about the fact that it's an LLM harness project. So I did a tabula rasa. Maybe the wrong decision, but we make mistakes. :) Originally I started to work on a form factor agnostic agent harness, but figured - we already have enough harnesses. So BeeZee's goal is to help manage multi-node, multi-harness, multi-human systems a bit easier. Yes it was 99% written by LLMs. I wrote the prompts, roughly 45% of the README and I handcrafted the logo. I promise the README has 0 (zero) emojis! I used Shadcn for the frontend. I still find it much better than Claude Badges with Dots (TM) and GPT Cards (TM).

Current features: - self host the local server and the cloud relay - access your local dev nodes' filesystems - discover Calude Code and Codex harness on your machines - spawn Codex/CC terminals sessions through a relay or start CC Remote Control sessions - resume sessions from both harnesses -> they have a shared memory in that sense - track high level token usage over time for all connected nodes -> it's one of the key development areas, Codex buggy ATM - visualise and manage installed MCP servers and CLI tools - upload files and folders to your remote dev machine -> it was kind of an emergent feature but I find it really handy! - has a paywalled managed relay under app.beezyai.net -> I'm poor so why not

Please if you find it useful or interesting star the repo, contribute, submit issues and enjoy!

Similar Projects

Developer Tools●●●Banger

Agetor - An open-source Harness Orchestrator

Git worktree isolation plus MCP approval interception beats terminal tab hell.

Big BrainSolve My Problem
drakochack
4229d ago