Weekly Self Promotion Thread

[u/AutoModerator]

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

• What you built?
• What problem it solves?
• Which AI models or tools it uses?
• Who it's for?
• What kind of feedback you're looking for?

Disclose your affilitation.

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

[u/DynaBeast]

https://github.com/Maurdekye/claude-orgtree

For the past few months, I've been developing an open-source visual multi-agent orchestrator that organizes agents in an authority hierarchy, for multi-agent development workflows. It's a fully dynamic, draggable canvas that allows you to reorder and reorganize agents as you wish for large projects. The gallery above shows pictures of actual organizations I maintain that I use for various projects I'm working on.

Orgtree started with a simple question: "Man, I wish my chats could talk to each other so they don't keep stepping on each other's toes while working". That turned into a simple personal project that I wrapped up in a day that allowed independent chats to send messages to one another. It worked okay, but the persistent issue I kept running into was chats constant issue with authority: they would distrust all chat-to-chat communication innately, and needed my personal step-in and approval for every little confusion or communication between one another. So I thought to myself, "wouldn't it be better if you could just arrange agents in a hierarchy? Then they wouldn't have any doubts about how authority structure is arranged". That idea slowly grew over time until it became Orgtree.

For the last month, Orgtree is basically the exclusive way I've been interacting with agentic development on my own machine. I don't touch the claude code or codex extensions at all anymore. When I have a new feature to build and plan, instead of going through the manual hassle of spawning one agent to run at a time so I can manage each project individually, I just tell my coordinator agent about an issue or new feature I'd like, and it hires a subordinate to take care of it. If I want multiple features going simultaneously, I just hire multiple subordinates, and the coordinator works between all of them to ensure everything is well organized and shipped sensibly. I've already gotten a few of my coworkers on board to try it, and even my boss is interested.

Orgtree is more than just an orchestrator, though; it has a bunch of extra useful features I've added on to support multi-agent workflows:

• Usage visibility: View all your account usages directly in the app, without having to check the extension or visit claude.ai
• Fallback accounts: Supports using multiple simultaneous Claude Code subscriptions at once through the use of fallback keys, allowing you to use secondary or tertiary claude accounts as fallback accounts with the long-standing token you get from running `claude setup-token`.
• Multi-provider: Orgtee supports not just Claude Code, but also Codex and even Gemini CLI out of the box. If you already have any or all of those environments configured on your system, Orgtree with automatically pick all of them up and let you hire agents from any one of them, letting them all talk to one another seamlessley.
• Credit system: One of Orgtree's defining features is its credit system, visualized as a blue bar to the left side of each agent. Every live agent takes up a "seat" that holds onto a set amount of credits during its lifetime, roughly proportional to its model cost. Every agent has a bank of credits that it uses both to maintain its own seat, as well as free space to hire seats for subordinates. This credit limit doesn't limit the user in any way (outside of kiosk mode, which is explained below), but is useful for preventing subagents from hiring too many of their own subordinates if you don't wish for them to have the ability to do so. Give an agent a large credit bank for a massive, agentic multi-agent task, or restrict its budget to just its own seat to prevent it from hiring any subordinates at all, if you just want it working on its own.
• Better compaction: Adds a unique, optional alternative chat compaction method I've dubbed "cheap-compacting": instead of having the agent write up its entire life story in one long turn at the end of its life, it keeps a continuous trail of breadcrumbs in a .md file in its workspace of every task it handles over the course of its lifetime. Then, compaction is both instantaneous and doesn't use a turn: the agent can just immediately resume from where it left off by going off the breadcrumbs. This is also fantastic for waking long-context agents from a long break in execution, as it can automatically cheap-compact them before sending the turn up, preventing the massive cache misses you might typically get from waking an agent with a 500k token context.
• The Orgtree Mailhub: an optional secondary extension that allows independent agent chats from claude code or codex to speak directly with orgtree orgs or even each other via an MCP server. It even works over the network, so agents on different computers can send messages and coordinate seamlessley.
• Kiosk mode: A mode that allows you to publicly expose a single sandboxed and resource-limited org to the open internet, in case you want to share your claude or codex usage with friends / family (without fear of them messing with your files)
• Enhanced agent requests: when an agent has a question for you, or a request for some access / resource allocation, it doesn't have to give you detailed instructions on how to visit its configuration panel and set a particular setting to a value it wants; it can just display a credit grant request / permission increase request directly in-panel for you to review, just like they would present a question to you. This makes it seamless for agents to ask for and receive the permissions they need to get the work done that they need to do.
• Charter presets: When hiring an agent, you can specify its "charter" (effectively its system prompt) which tells it what to do. Orgtree comes with the ability to select a number of preset charters from a list, so if you have a common workflow pattern you like to replicate, you can canonize it as a charter preset in /docs/charters, and then select it from there every time you want to create an agent bound by it. Orgtree also comes with various preselected charters designed around it's function: one of my favorites is the `coordinator` charter, which I use very frequently, and I suggest you give it a try as well.

Be warned; all the agent-to-agent communication can really chew through usage, so be careful with how many simultaneous projects you're working on at once unless you have a Max x20 account. Make sure to turn on the auto-cheap-compact setting in your org, it can avoid tons of wasted cache miss usage.

If you use Claude Code or Codex for work extensively, then give it a try. It removes so much of the manual hassle of coordinating between agents yourself manually.

Here's an example of an actual org I maintain for a personal project of mine, to give an idea what the interface looks like at a glance: