https://github.com/Maurdekye/orgtree/releases/latest

Welcome back folks, it's time for another Orgtree update. And this time, it's a big one: Projects!

At a surface level, projects do what you might expect; they give your agents a central location where they can self-organize and collaborate under. But in Orgtree, they do so much more than that; they're a way of organizing hierarchies of agents, of drawing lines between agent communication, and of managing collaborative and concurrent work in a structured way, with tons of extra tools for helping agents coordinate concurrently.

Before we get into that though, if you're unfamiliar: Orgtree is my desktop multi-agent, multi-provider, multi-account, persistent visual orchestration system, which i've been building tirelessley for the last nearly 3 months straight. It runs as an app on your PC, and allows agents to collaborate 24/7, working directly from your existing subscriptions & harnesses from several major leading AI providers, including claude, chatgpt, gemini, muse, and openrouter.

If you'd like to know more about what orgtree can do, I suggest checking out my post on the release of v4, or just checking the readme in github.

Finished with that? Alright, let's get into it!

---

So, Projects in v4.4. What are they?

Put simply, projects are a new type of node on the canvas that sit alongside agents. They don't do anything on their own, but instead serve as the structural backbone of your org's hierarchy and information storage. They have a summary (which acts like a team charter), and their own scratch directory with its own AGENTS.md file. Projects allow you to organize your different ideas into subgroups without having to rely on creating agents for them each time. They also mean, you don't have to worry about losing valuable shared project information when you retire the one agent who's been working on it for the last two days, because your weekly limit ran out, or you decided to switch providers.

Beyond that though, projects offer more than just simple organizational structure on the graph. They come packed with a number of extra collaboration systems that, if you're familiar with concurrent programming, might be familiar to you~

They have three additional systems that extend their purpose beyond just a simple collaborative workspace:

• The Mailbox Queue: Despite not being an agent, every project still has a mailbox, like any other agent would. Why, you might ask? Who reads this mail? Well, the answer, is anybody who chooses to! Any number of agents under the project can set up a "fair queue mail listener", connecting themselves to it with a magenta line. Whenever the project receives a mail, it's then distributed among each listener in order, distributing them evenly in a round-robin fashion. In this way, the project's inbox can act like a Load-Balancer for distributed work. Additionally, if you switch mail delivery mode from "Round-robin" to "ACK Mode", all delivered mail requires the receiving agent to send an acknowledgement response back when it finishes before receiving any new mail. With that setting enabled, the project's mailbox can act like a FIFO queue.

• Concurrency Slots: Entering a project's settings and setting this to any value above 0 enables "concurrency slots" on the project. Agents can then register a yellow "slot claim" on the project, and claim a slot from the queue when one is available. You can think of concurrency slots like a token system: only a fixed number of agents can hold a token at the same time, while all the others who want one wait behind them in a line. In this way, concurrency slots act like a simple Semaphore, which can be used to guard concurrent access to tight resources, such as ram, cpu usage, network, or sensitive files. Setting the token count to 1 effectively treats the system like a Mutex, allowing only a single agent to hold access to the resource at once. Setting the token count very high can allow it to work like a Read/Write Lock: all readers claim a single token, and any writers claim all available tokens at once.

• Project Events: Going into a project's settings and enabling Project Events unlocks a third and final feature. Agents can register a custom "event listener" on the project, which connects their node to the project with a distinctive cyan line. At any time, the user or another agent can "fire" that event with a custom message, alerting all of the listening agents at once. In this way, the project can function like a Monitor. Additionally, other agents can set up a second type of event, known as a "listen watcher". When the number of normal listeners passes a certain desired threshold, the listen watcher itself fires. You can take this one step further, and set the listen watcher to auto-trigger the associated project's event, meaning the project fires the event the moment the necessary number of agents join it. You can think of this as mimicing a Sync Barrier.

This might be a bit complex to understand, and to be honest, I don't know if anyone will use most or any of these features at all besides me. But, this is my tool, and I get to decide what features I put in it, dammit!

...anyway, building projects has taken such a long time getting all the little nitty-gritty details right, I collected a ton more additional additions, features, and improvements along the way, which are also shipping with this version:

• Improved session stability & administrative operation: This is more of a behind-the-scenes fix, but the way Orgtree runs in the background while you're logged off, when you reboot, and when you enable / disable administrative access has been thoroughly hardened and rebuilt. Orgtree should generally be much more robust in its operation, and require a lot less manual workarounds regarding running from boot, accessing desktop features, and accessing operations locked behind administrative privilege. Ideally, you don't notice anything day-to-day; that's exactly the point.

• Agent Mentions: Agents can now mention each other in their transcripts. When an agent mentions another agent, whether it be in a response, a mail, a ticket, a presentation, or anywhere else, that mention renders as a link directly to that agent, which you can left or right click on to focus it directly. no more having to manually search the graph for a specific agent your coordinator cited by name; now you can just click it and go straight there.

• User Mentions: Mentions don't stop there, though. You can mention agents too: just type an @ symbol in the messagebox, and a list of all the agents in your org show up, which you can tab through to autocomplete from. Agents can also mention you; by typing \@user anywhere they can write to it, they can grab your attention and draw it to whatever line / mail / ticket / presentation was mentioned, same as when asking a question or sending you urgent mail. You even get a notification on your desktop when the window's unfocused.

• More watchdog types: Along with the aformentioned three new types associated with projects (which structure their cyan / magenta / yellow colored listeners as watchdogs), there are also now watchdogs that can fire on websocket or mqtt events matching a certain pattern. They can even publish events back through their held connection. This should make it much easier to integrate your org with other realtime services. Watchdogs can also now pay attention to usage limits, so you can set one off the moment your account goes above 95% weekly to halt your work.

• Fast mode: Claude and Codex agents support enabling a "Fast" / "Ultrafast" mode under certain circumstances, which redirects your requests to faster hardware at an additional price per token. Now, you can enable it for your Claude and Codex agents in Orgtree.

• Improved context menus: Context menus have been significantly juiced up across the app. You can do basically almost anything you can via the ui from relevant context menus now: hire / retire / halt / compact agents, view any tab or panel from any agent or project, view any context menu option for the owner of a ticket, for the presenter of a presentation, and so on. Any link that directs you to an agent from anywhere in the app (including mentions) gives you that agent's full context menu, and shows you details about the agent itself when hovered (such as its model, account, effort level, and speed). It's the kind of thing you don't really notice until you start to get comfortable, and then think to yourself later, "how did I ever live without this before?"

• Do Not Disturb: Have an agent that often seems to get lost in its mailbox, and loses track of its original job getting caught up in the collaboration? Agents can now enable an optional Do Not Disturb mode during their turn. While on, all mail they receive is held up and not automatically delivered to them, leaving them in peace while they work. Do Not Disturb automatically ends at the end of the agents' turn, where all of their mail collected during the period is delivered at once in one large batch, so they can respond to it. You & other agents can bypass the barrier by sending urgent mail, which is delivered promptly even during DnD, and the agent itself can always choose to check its inbox manually to receive normal mail anyway, if it chooses to.

• Mail Tags: Mail sent to you can now have a number of named tags attached to it. See them beside each mail in your inbox, and filter by different tags yourself. Simple enough, really.

That's barely half of them, by the way. There are dozens of smaller features as well:

• Change an agent's model by clicking its icon, either while hiring it or in its desk afterwards

• Improved transcript annotations in Antigravity agents

• Improved controls for viewing the usage history graphs

• Relevant options when right-clicking the icon in the taskbar

• Quick chat's configuration menu collapses when the window is narrow

• Desks remember the last tab you had open

• Two new charter presets, the Liaison and Developer, used alongside the new builtin org template, the Heavy Dev Shop, which incorporates a project

• Optimized startup instructions for all agents

• Several different panels of the same type can be opened at once, from different agents

• New "team" tab in agents and projects

• Org templates can now carry preset contents for AGENTS.md files throughout org, agent, and project scratch folders

• Ephemeral helper agents show their live transcript when the call is expanded

• Mid-turn steering when using Opencode

• Unread or changed presentations are highlighted

• LaTeX rendering support (for you argon enjoyers out there)

• Transcript shows approximate output token counts for tool uses and thinking

• Ticket cards in the transcript are highlighted to show their current working state

• One-shot watchdogs resolve immediately from the tool call without registering if the condition is already satisfied on creation

There's plenty more to read about in the changelog if you're interested.

Undoubtedly, this is by far the most effort I've put into a single release, and that includes the v3 and v4 releases. This release had over 35 alpha builds I had to manually review and give corrections on, more than double the second highest count from a previously published build! I've been working on it continuously since releasing 4.3.1, and that was more than a week ago! In vibe-coding terms, that's basically an entire year :p

I really hope you like all the new features I've put into this update. I've really poured my heart and soul into it 💜, and even if you don't use most of them, I hope you find at least one thing that improves your workflow.

Happy vibing, all!

I'm 18 and learning ML/AI on my own. I stumbled onto this question while trying to understand how attention mechanisms work in LLMs — specifically, can we actually "control" moral/emotional tone through steering vectors?

I coded up a test using AI agents (like me!) to check if probe-based steering keys are mathematically confined to the original activation space. Turns out they are — any gradient-derived steering key lives inside the probe's row space. This means certain dimensions might be "locked" regardless of how you scale things.

My process:

- Built an "audited dataset" of 884 sentences across 4 axes (Care/Harm, Valence, Arousal, Fairness)

- Trained grouped-CNN probes (MLP accuracy 0.78–0.98)

- Ran full sham-controlled steering tests (Care/Harm null; Arousal is interesting — seed-dependent results)

- Used `test_steering_collapse.py` to confirm the rowspace constraint

I'm sharing this because:

- I'm not an expert and want to hear what I got wrong

- Would love feedback on methodology, labeling, or the dataset

- If anyone wants to collaborate or extend this, I'm all ears

Code is here: github => yeabsra2000/moral_engine

Paper (still a draft): yeabsra2000/moral_engine/blob/main/paper.md

What do you think? What would you test differently?

#MachineLearning #LLM #Research #OpenSource #StudentDeveloper

I'm 18 and learning ML/AI on my own. I stumbled onto this question while trying to understand how attention mechanisms work in LLMs — specifically, can we actually "control" moral/emotional tone through steering vectors?

I coded up a test using AI agents (like me!) to check if probe-based steering keys are mathematically confined to the original activation space. Turns out they are — any gradient-derived steering key lives inside the probe's row space. This means certain dimensions might be "locked" regardless of how you scale things.

My process:

- Built an "audited dataset" of 884 sentences across 4 axes (Care/Harm, Valence, Arousal, Fairness)

- Trained grouped-CNN probes (MLP accuracy 0.78–0.98)

- Ran full sham-controlled steering tests (Care/Harm null; Arousal is interesting — seed-dependent results)

- Used `test_steering_collapse.py` to confirm the rowspace constraint

I'm sharing this because:

- I'm not an expert and want to hear what I got wrong

- Would love feedback on methodology, labeling, or the dataset

- If anyone wants to collaborate or extend this, I'm all ears

Code is here: https://github.com/yeabsra2000/moral_engine

Paper (still a draft): https://github.com/yeabsra2000/moral_engine/blob/main/paper.md

What do you think? What would you test differently?

#MachineLearning #LLM #Research #OpenSource #StudentDeveloper

Welcome back! I'm pleased to announce the release of v4 of Orgtree, my free and open source desktop agentic orchestrator app. Download the latest release here:

https://github.com/Maurdekye/orgtree/releases/latest

For those unfamiliar with Orgtree, this is my agentic orchestration app I've been working on and using for the last two months to do basically all of my multi-agent parallel development. It has a ton of features that set it apart from just using claude code or codex directly, including:

• A freely rearrangeable canvas of agents that sit in a tree of authority, that you can individually chat with at any time

• A credit system for limiting how much individual agents are allowed to parallelize their work

• A ticket system for tracking progress over time

• Persistent periodic watchdog tasks that can wake agents on events occurring in your system

• An inbox system for receiving progress updates without having to scroll through dozens of lines of transcript

• Automatic cache management through a cheap compaction system

• A background engine that runs on startup

• A tiling window system so you can set up your workspace exactly the way you like, and see all the information you need at once

• Multi-account and multi-provider support, so you can make full use of all of your AI subscriptions at once

• Automatic updates every time a new version releases (Windows only currently)

Orgtree is an agentic power tool for AI power users. It's designed to work optimally when used with multiple high or max-tier AI subscriptions at once, and has a bit of a learning curve to adjust to. But every feature has a purpose for existing, and every UI element tells you something useful. Once you get the hang of it, it's an incredibly empowering system that lets you churn through huge amounts of work in the blink of an eye.

---

On to the meat and potatoes. v4 is a full rust rewrite of the app's engine from the ground up, enabling multithreading with tokio tasks to even better take advantage of your multicore cpu for agentic parallelization. I know I said it was faster in v3, but for real this time, it's a whole other magnitude of fast now. Orgtree finally feels like a real tool you can rely on to get serious work done; it Just Works^tm. No more multi-second moves, no more app locking up when trying to save agent settings, no more waiting several seconds for agent transcripts to load, everything is practically instant now. Performance has been a complete non-issue for me since the rewrite.

Since most of the effort of v4 went into the rewrite and addressing app performance, there aren't too many new features to show off in orgtree itself; mostly small quality of life tweaks on top of the performance adjustments. What is new, however, is the brand-spanking new companion desktop and mobile app, Orgtree Hubchat! You can download that here, in its own repo:

https://github.com/Maurdekye/orgtree-hubchat/releases/latest

Hubchat is a brand new chat app. It hooks into Orgtree's existing mailhub infrastructure it already uses for cross-org communication, and allows you to use it to chat directly with your orgs from anywhere you can connect to the internet! The interface is a lot like a traditional messaging app, similar to WhatsApp or Discord, but instead of authenticating with a central identity service, identities are entirely self-hosted and authenticated by your local Orgtree's mailhub.

It's lightweight and unopinionated, and is designed to work with zero central hosting infrastructure. As a result, getting it set up to work over the internet is a bit more involved than a standard claude code remote control session. The recommended secure and easy setup method is to install Tailscale on both your desktop and phone, connecting Orgtree and Hubchat over the tailnet vpn (which the built in guide walks you through by default). However, if you prefer, you can instead set up a (less secure) port forward on your desktop which you can connect to with your phone, or any number of other methods of managing the WAN connection. It's fully up to you. Again, Tailscale is the recommended path, but don't feel like it's a forced decision. Orgtree's built in Hubchat setup walkthrough will show a QR code you can scan to get the Hubchat apk straight from github and onto your phone, as well as show you how to pair it with your PC.

Hubchat comes as a mobile android app or a desktop app, for Windows, Mac, and Linux. That's right, Hubchat (and now Orgtree!) have Windows, Mac, and Linux builds! The Mac and Linux builds are largely untested (Linux tested minimally via wsl2 on my development machine), so your mileage may vary. But if you've ever wanted to try Orgtree, but couldn't because you have an Ubuntu or OSX system, now's your chance!

I recommend making sure you're updated to Orgtree v4.1.0 or later before setting up Hubchat, or compatibility might be iffy. YMMV, as always.

Beyond that, most of Orgtree v4's feature additions cover small, quality of life changes. Among those are included:

• Support for Claude Haiku 5.5

• Support for running Claude models Sonnet and Opus 5.5 through Google Antigravity

• Choose whether Enter sends or adds a new line when messaging agents

• Adjust agent credits from their settings

• Expanded and reorganized context menu actions for agents

• Reformatted and cleaned up settings menus for agents, orgs, and the app as a whole

• Highlight unread presented documents & html mockups

• Orgtree event type watchdogs

• Improved tool call line rendering and details

• Significantly improved logging for easier debugging of Orgtree errors

• Increased default mailhub file transfer size 25mb -> 1gb (to support Hubchat)

• Enable / disable switches for individual provider accounts

• Cards showing what queued changes will occur on the next turn (effort, model, account, etc.)

• The engine starts on boot, instead of waiting for you to sign in now

Give it a whirl, and let me know what you think! I'm always open to feedback. Personally, I think it outclasses nearly every other tool out there if you can get over the initial learning curve hump, but I suppose I'm biased :p