Link to the paper: https://gking.harvard.edu/peerless/

Seems like all of the complaints about AI generated reviews being low quality don’t stand up to scrutiny

same as the title.

I had to put this on a GitHub because it’s too much text from here plus all would be too much work copy paste anyways, but this is the behavioral architecture of Monday. Not a simple system spot. This isn’t sounds sarcastic like Monday. This is how does Monday react to this situation? What conditions act differently? Also very handy techniques for staging, larger models, and smaller constrained environment. Including one that has a 30% reduction in the amount of space it uses in vram with no loss of efficiency

As the title says, I don't have a 5 hour limit, I can use up all of my weekly usage at once if i want. I am a plus user and I think pro users are the ones without the 5 hour limit.

For the longest time I thought this was how it was but after getting another plus account i got confused looking at the 5 hour limit, so why is this?

Some context: around July openai had removed the weekly limit and that's the time when I subscribed so can it be some kind of left over thing?

🚨 Hiring: Senior System Analyst (.NET + Power Platform + RPA)
🏢 Gilead Sciences | 📍 Foster City, CA (Hybrid) | ID: 17351
8+ yrs exp in C#/.NET, Power Apps & Blue Prism/RPA.
1000s of recruiters will ping you—consider this your heads up!
🔗 Senior System Analyst/ Developer (.NET, Power Platform, Python, RPA technologies) in Foster City , C…
📩 Raj@rangam.com

I have a theory on the reason for all the resets

I believe the reason they’re doing this is so that people especially on the pro plans with Dot and Codex and Work will be accustomed to being very heavy users and then when they stop doing resets, they hit the usage limit and they’ll have to either upgrade or buy credits.

I am especially concerned for power users on the pro $100 a month plan, especially those who rely heavily on dot after this month when they start imposing usage limits on dot.

So I think the whole thing is actually a strategy by OpenAI to sell subscriptions and credits in the end.

Just my take.

I’m a longtime Codex guy that’s feeling pretty burnt out on the spotty updates and game of resets. I’ve heard Claude gives more stable and reliable outputs and performance. One thing I’m curious about is that I’m on the 20 dollar plus plan with ChatGPT, so would be looking at the equivalent pro plan with Claude. But I have been able to get huge amounts done with codex lately on account of all the constant resets. So my question is (and thank you for sticking with me!) am I going to get a solid amount done on clause under the 20 dollar monthly plan? Or is it gone in the blink of an eye? I really think I’m ready to make the move so looking for reassurance more than anything. Opinions very welcome, and thanks in advance!

Apparently I used all my work credits.

I've been on the business plan since July under the "buy 1 seat, get 1 free for 48 months" promo.

A few days ago I had accidentally let one of those seats renew as a premium seat (Yes, I know, this is a mistake on my part). I had read online that support might do a prorated refund, so I opened a ticket. The entire request was essentially: "I accidentally upgraded one of these seats to premium at the start of the billing cycle. Would it be possible to downgrade it back to standard and get a prorated refund?" Nowhere in my request did I ask for cancellation/deactivation.

Rather quickly I got a cheerful email back: Refund processed! Also, your workspace has been cancelled and deactivated.

I shit myself in panic when I read that. I did not want to lose that golden promo that isnt given out anymore. I responded as soon as I saw the email but have now been told multiple times that i'm SOL.

I've spent the past few days going back and forth with a "human" (genuinely can't tell) and here's where it stands:

* They acknowledge the plan was cancelled by mistake.

* They say there is "no way" to give me back a plan with the same promotional terms.

* Their solution is that I resubscribe at full price.

So the deal I was locked into for 48 months is gone, not because of anything I did, but because someone (something?) on their end misread my request. I need this for work, so I don't really have a choice but to resubscribe. That's an extra $25/mo for the ~44 months left on the promo, roughly $1,100 to fix a mistake they admit they made.

Posting this as a PSA because I googled before opening the ticket and nothing warned me this could happen. If you're on ANY promotional OpenAI plan, think very hard before you let support touch your billing, for any reason.

Also, has anyone actually gotten a promo restored after support broke it? What should I do now?

Been poking at this for a few days and wondering if anyone else noticed.

First I uploaded a generated beep (test-2.wav, literally nothing else in it) and told it to describe it without python or any code. It said steady high-pitched electronic tone, like a test signal, no voices. Correct, and no code ran at all.

Then a Russian emo-rap track, heavy autotune, 808s, renamed to shfm.mp3 so the filename gives nothing away. It opened python, read the first 26 seconds with soundfile and just did display(Audio(chunk)). No whisper, no ASR, nothing else in that cell. After that it got the hook pretty much right and described the song correctly: instruments, structure, what the lyrics are about. The parts it got wrong were exactly the parts I can't make out myself either, which is not what you'd expect if it just remembered the song.

On another track it even replayed a chunk at 0.9x speed, like it was trying to catch a fast verse, and ended up with around 70% of the words right.

The weird part: the model itself doesn't support audio input. Through the API it just doesn't take audio, and in Codex I couldn't get it to listen to anything. Even in the web version the tool once returned "you do not support audio" to it mid conversation. So whatever does the listening lives only in the ChatGPT web harness. The help page for the new audio uploads mentions "audio understanding and transcription" and says it depends on the selected model, but nothing about how it actually works.

Anyone know what's going on under the hood? Is there a separate audio model handing the main one a description, or some audio path the API doesn't expose? Has anyone gotten anything similar working through the API or Codex? And if you've tested it on music, how good is it for you?

(model: gpt-6, Extra High)

I get error "Your usage does not need a reset right now". My weekly usage is 13% and I want to use the reset before it expires. What malpractice is this?!

Edit: Seems like, when Tibo "forces" a reset, banked resets are blocked for some time (?). And OpenAi does a poor job in communicating that in their App. Terrible UX.
Edit: Apparently, one must be under 80% to use a banked reset. Again, terrible UX.

WTF, it’s 5 minutes until my banked reset expires, but I cannot reset from 87% because OpenAI reckons it’s not needed. So 13% stolen, right there, promised but not delivered. Not on.

Anyone else experiencing an insane increase in usage? I blew through my five hour limit with one question, twice in a row. Same basic type of task that Claude handles using less than 5% context.

I had stopped my subscription because I preferred using Claude but received a free month of Plus subscription. I hadn't used it in a few weeks beforehand but I never came close to hitting a 5 hour limit before without serious effort. Now, I've literally hit it twice using a reset and the task didn't even finish. I am thinking about ending even this free subscription and uninstalling unless there is some acknowledged bug with useage rates...

If it’s going to expire, at least let it activate before it disappears…

I am searching for inspiration. How do you let ChatGPT with scheduled tasks/vibe coding projects improve your quality of life? It is not about playing around and creating the xth dashboard, but solving real problems with ChatGPT.

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 an IB student, and something happened in class today that got me thinking.

I heard someone mention that our school’s Wi-Fi had blocked access to AI tools. Around the same time, another student said they struggled to read articles because their attention span was too short.

Those two comments made me think about something bigger than either situation individually.

Schools are increasingly trying to control how students use AI, often because of concerns about cheating, independent thinking, and students relying on technology to do their work for them. Those concerns are understandable.

But at the same time, what does it mean if students are struggling to engage with the material they’re supposed to learn from in the first place?

Reading a long article requires patience. You have to follow an argument, understand context, question claims, and connect ideas. If you replace that process with an AI-generated summary every time, you might get the information faster without necessarily developing the ability to understand it independently.

On the other hand, simply blocking AI doesn’t magically teach anyone to read more carefully or think critically.

So are schools addressing the actual problem, or just restricting one of its possible symptoms?

I’m not arguing that AI should be allowed everywhere, nor am I claiming that AI is causing shorter attention spans. Two comments in one classroom obviously aren’t enough evidence to establish that.

I’m genuinely interested in what other people think:

-Are schools approaching AI restrictions the wrong way?

-Do you think short-form digital content is changing how students engage with longer texts?

-Should schools teach students how to use AI responsibly rather than primarily trying to prevent access?

-Could AI actually help students develop better reading and critical-thinking skills if it’s used properly?

I’m especially interested in hearing from other students and teachers. Have you noticed similar things in your schools, and how are your teachers responding?

I think there’s a bigger conversation here about what education should look like when information is increasingly easy to generate but genuinely understanding it still takes effort.

PS; one last note i'm genuinely worried if we lack the capacity to comprehend text how can we protect ourselves from misinformation, reading is power, literature ia power, it feels as though this is a massive stab upon my heart how will my generation continue to be human if all we understand is dumbed down passages, even in the most rigorous curricula graduates lack these 4th-5th grade skills.

Has anyone actually been banned due to sharing their account with a single friend? My uni major doesn't provide an account, whilst my friend's one does but he doesn't use it, so i'm wondering how much of a risk this actually puts on his account

I can't tell if it's human work or ai work I mean I got from ai but this is too much no? I can say oh that bottom right one I fed the picture to get it. Other wise everything else I made it by hand or 3d rendered. We are not safe anymore because we won't be able to tell anymore. Or it could be stolen... Either way it's bad? Mostly

Well OpenAI won't be replacing my job because I can literally program faster than this thing.

JESUS CHRIST....

Asked it to add a button to a WPF project and 25 mins later it's still working on it. hahaha 10 mins in I decided to just do it myself... I'm done and it's still working it out.

We'll be telling our kids about the glory days when AI could get things done faster than humans.

On the Plus subscription plan right now and it expires on the 28th. My banked reset expires on November 6th. So can i use the reset if I'm on the Free plan or does the reset have to be used before my Plus subscription expires?