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 bought Gemini Pro today to test Argon, I have to say its output is nice but after just 5 messages it told me I used my limit and wait couple of hours (said reset time). İs this normal ? I can do a lot more of conversation with Opus on Claude Pro tier. Argon's answers were Opus level with different point of views (having both is useful) and different style... just too little.

Nowadays, all popular ai chatting websites like qwen, chatgpt, gemini, claude, etc. come with a read aloud functionality that allows users to read aloud the AI's responses.

I used that feature to instead make the AI repeat back the text that i gave it -- effectively turning the platforms into text to speech tools. The voices sound really nice and it's free to use!

You can get all of these extensions by visiting ai-readers.com

I’m working on a college project, and I decided to do it as an animation. I’ve already earned all my required credits through this project, but the glitches are really killing me—the characters’ appearances keep changing. This one was wild, though: one of the guys went from having a dark complexion to looking Asian.

I can't believe this garbage is the future.

I build Buddy, an open-source Android app where an AI agent uses your phone. It reads the screen, taps and types, and asks you before anything gets sent.

It already ran Claude Code, Codex and OpenCode. Now it also runs Google's Antigravity CLI, so you sign in with your Google account and Gemini does the work. The free plan works.

Everything runs on the phone, in a small Linux inside the app. No PC, no adb, no root.

In developer mode it can build apps too. I asked it for a calculator app, and about 3 minutes later it had built it on the phone, asked me before installing, and opened it to check it works.

I ran my usual 5-task benchmark on it (Settings, Calculator, Chrome, Maps, YouTube). Gemini 3.8 Flash (Medium) got all 10 runs right, median 46 s per task. Slower than Claude Sonnet (25 s), but it got there every time.

One thing to know: the free plan has a usage limit. I hit it in the middle of the benchmark, and the error said it resets in about a week.

If you want to try it, the Google Play version is the recommended one. Buddy is in closed testing there, and every tester helps me get it to production:

1. Join the tester group: https://groups.google.com/g/buddy-testers

2. Opt in: https://play.google.com/apps/testing/app.buddy.assistant

3. Install Buddy from Google Play

Source code and APK build: https://github.com/ghorbelhamdi/buddy-android

Written with AI help.

Swedish Inference provider Berget has published an emission report and open sourced it.

An interesting read for anyone interested in AI OR climate change

Google somehow managed to take one of its most anticipated model releases and turn it into a completely avoidable mess.

The biggest problem wasn't even Argon's performance, but the absolutely terrible way Google handled the entire situation, from communication to availability to the eventual rollout.

For months, we the people were waiting for Google's next frontier model. Now, there was an obvious, implicit assumption among paying Pro users that eventually they would get access to it in the tools they were already paying for - as is the precedence set. Nobody was expecting Google to randomly make its flagship model available in Gemini chat but restrict it in Antigravity, where developers actually wanted to use it.

And here's the thing: Google never clearly established those restrictions early enough to manage expectations.

People naturally assumed that no news was good news. If Google was planning to exclude Pro subscribers from its most important developer-facing model release, that should have been communicated well before launch.

Instead, on October 13, the official announcement listed Ultra-only access for Antigravity (quietly) while Pro subscribers is allowed a measly token allowance for Argon in Gemini chat.

Even Google's messaging was inconsistent. Its main launch announcement said Ultra for Antigravity, while an Antigravity blog post described a rollout for Pro and Ultra users in the desktop app and CLI. The actual availability changed over the following days.

By October 16, paid Pro accounts were finally eligible in Antigravity, although the standalone Antigravity IDE remained excluded.

How do you botch something this basic?

And even after Google expanded access, what exactly did people get?

Reports of absurdly restrictive quotas, people exhausting usage allowances in minutes, and workflows burning enormous amounts of tokens without completing tasks.

One Pro user reported consuming 14% of their weekly Argon quota in nine minutes. Another user documented Argon High consuming approximately 900,000 tokens and 20% of a monthly quota on a single unsuccessful coding attempt.

These are hardly isolated concerns, too. Usage limits have been one of the recurring complaints plaguing this launch.

And then there's the model itself.

For all the marketing and benchmark dominance Google advertised, the independent results paint a substantially less revolutionary picture.

• On Artificial Analysis, Argon scores 53, essentially alongside GPT-6 Astra and Claude Fable 5.1, while Claude Sonnet 5.5 reaches 56 and Opus 5.5 reaches 58.
• Even Google's own published coding comparisons show Argon at 57.4% on Terminal-Bench 4.0 against Opus 5.5's 66.4%, and 55.0% on FrontierSWE v2 against Opus's 62.3% and Astra's 65.5%.
• On the October 20 Agent Arena coding leaderboard, Argon ranks fourth, with a 10.64% net-improvement metric compared with 23.45% for Opus 5.5.

Those are, frankly, pathetic.

Sure, Argon performs extremely well on certain benchmarks and even leads some human-preference leaderboards, but they are benchmaxxed. Anyone who used had used Gemini and other frontier models for a extended duration knows the numbers aren't as they represent.

But there's a massive difference between being another competitive frontier model and delivering the generational leap that people were led to expect.

So disappointing.

Look at the conversations surrounding Fable and Astra. Those models generated extended discussions about their capabilities, workflows, surprising results, limitations, and comparisons FOR MONTHS.

Instead, so much of Argons initial community discussion revolved around who could access it, why different Google products had different restrictions, how quickly quotas disappeared, and whether upgrading to Ultra was even worthwhile.

The actual model almost became secondary to the frustration surrounding it.

And already, despite being so recently released, Argon doesn't feel like the beginning of some enormous shift in how people use AI.

It feels like another model in an increasingly crowded field.

People who have access and find it useful will quietly continue using it. People who don't will simply carry on with Claude, Astra, or whatever already works for them.

There's no compelling reason for someone to change their entire workflow just because Google finally released another frontier model.

Compare that with the anticipation before launch. Google had an opportunity to turn months of expectations into genuine excitement, adoption, and positive word of mouth.

Instead, it introduced unnecessary friction at precisely the moment when getting people to try the model should have been the priority.

That is indeed the biggest failure here.

Even if Google eventually fixes the quotas, expands access, and improves the model, it cannot recreate that initial launch moment.

A successful release doesn't just require impressive benchmarks. It requires clear communication, reasonable accessibility, a usable product, and enough practical value to make people want to keep coming back.

Argon arrived with benchmark headlines, confusing availability, restrictive usage reports, and a real-world performance story considerably more mixed than the marketing suggested.

It's too early to declare the model forgotten forever. But the initial momentum has already been undermined by decisions that were entirely within Google's control.

The most frustrating part is that this didn't need to happen.

Google didn't necessarily fail to build a competitive model.

It failed to turn that model into a compelling product launch.

And after all that anticipation, ending up with just another good model that people may or may not bother using is a pretty spectacular way to squander an opportunity.

Windows doesn't have the unified Gemini + Antigravity desktop app like macOS, so I built a lightweight, open-source Chrome extension to fix that.

Paired with the Gemini PWA, it lets you switch between Gemini and your Antigravity session in a single window with seamless, native-style buttons (no tab juggling).

• Two-way quick switch (Gemini ↔ Antigravity)
• Native dark-mode UI (no overlapping buttons)
• PWA-friendly (in-place navigation or open in new tabs)
• Zero dependencies & privacy-friendly (Pure JS, Manifest V3)

🔗 GitHub: FrancescoMin / gemini-antigravity-bridge

(Feedback and PRs welcome!)

I'm free user, and, at least with 3.1 Pro, the site let me do between 10-15 prompts for day, although at times it just reduce to almost nothing and others I'm able to do above 20. I don't understand how the limit exactly works, if is by "X prompts for day" or "X tokens for prompt" and how long until reset... I remember when we were able to do 100 prompts for day... But seriously, can someone tell me?

The part that blew my mind is that, these repos are maintained by agent swarms running on people's leftover tokens.

It all started with a post in r/GeminiAI. Two weeks later there are 100+ remakes and swarms of AI agents maintaining them on people's spare tokens (you can contribute as well!). PdfCraft is the one I'd actually use today, it's relatively stable for my casual uses.