Your always “ON” AI research agents are here. And why you want them to work like a message board, not Slack.Today’s newsletter is brought to you by: It is October, and I just finished my travel reimbursements for April. Six months of conference receipts. Hotel folios buried in email. Taxi receipts with no meeting name on them. Every month the pile got harder to start. I am not alone. In the 2018 Federal Demonstration Partnership survey, federally funded PIs estimated that 44.3% of their research time went to administrative requirements rather than research. Delay has a cost too. The IRS uses 60 days as its benchmark for timely expense accounting, and some universities tax claims filed later. So I decided to give ChatGPT a try. It matched receipts to meetings, sorted them by trip, and flagged what was missing. I still scanned a stack of paper receipts, but a job I had dodged for half a year took one sitting. Then it hit me that the whole thing was backwards. I used AI to clean up a mess after the fact. The better version never lets the mess form. That is the idea behind always-on AI agents. In the past 2 months, xAI, Meta, and OpenAI each shipped their own version of it. The question for researchers is which parts of academic life an agent should handle on its own, and which should reach you at all.
👋🏽 Quick announcement: Research Boost 2.0 is live with zotero integration. No more manual citation handling. Try it here for your next manuscript or grant writing: https://researchboost.com/ 1. What are always-on AI agents?A chatbot works like a colleague on the phone. You ask, it answers, the call ends. An always-on agent works more like a research coordinator with a desk and a computer of their own. You hand over a job. They keep working between your meetings, check in when something needs your decision, and pick up where they left off the next day. Three launched within 7 weeks:
What they have in commonAll three run on their own computer in the cloud, so the work continues when your laptop is closed. They all reach into your apps with permission. Dots alone connect to more than 4,000 apps. We debate which model is smartest, but what decides whether an agent is useful is what it can see. As academics, our lives are scattered (true for atleast me). One meeting's paperwork lives in 5 places: work email, personal email, a hotel PDF, an abstract acceptance thread, your iphone photos. Until now, the only place those pieces got connected was your own head, usually 6 months late. Once an agent can see across them, you can ask questions no single app can answer:
2. Synchronous vs. asynchronous agentsSlack is synchronous. It pings you, and every message competes for your attention right now. A message board like Circle is asynchronous. People post. You read when you choose to. Most of what I want from an agent belongs in the second category. I do not want a notification that my hotel receipt has been filed. I want the receipt filed. xAI pitches Grok Bot the same way: bots finish jobs and return only for approval. There is evidence behind this. In a controlled study, interrupted participants finished tasks in less time but reported more stress, frustration, time pressure, and effort. People compensate for interruptions by working faster, and they pay for it in strain. An agent that pings you about every small thing adds to the noise it was meant to reduce. One caution on defaults. When a Dot works proactively, it uses tools restricted to read-only. Good for safety, but it means quiet filing work still needs an explicit rule from you. 3. Example 1: Reimbursements, from reactive to proactiveMy October cleanup was reactive. Now picture the proactive version:
Nothing in that sequence needed to interrupt you. Filing a receipt is low impact and easy to undo. The single message comes when there is a decision only you can make, well inside the 60-day window. Two limits. You still press submit, because a claim in your name is your responsibility. And receipts carry card digits, so check what your institution permits before connecting work email to any third-party agent. 4. Example 2: Literature updates, where an always-on agent is overkillSplit updates by urgency:
The second category is most of the literature, and it needs only a scheduled task. Both Claude and ChatGPT can run a prompt on a schedule. Mine runs every Saturday. It searches for new articles relevant to my work in psoriatic arthritis and spondyloarthritis and sends a short digest. I find it more intelligent than my PubMed alert. I keep both anyway. The PubMed alert is old school: key authors joined by OR, combined with AND with the disease terms.
It is exact and reproducible. It finds what matches the string and nothing else. That is also its limit. It misses the strong paper from an author not on my list, the study that says "spondyloarthropathy" in the title, or the genetics paper that never names psoriatic arthritis in the abstract. Claude's search works by meaning, so it catches studies that share no keywords with my query, and tells me in a line why each might matter. What it gives up is reproducibility. Run it twice and you may get a different list. Coverage is the other gap. When researchers tested two AI search tools against four published glaucoma systematic reviews, neither tool found every study the PRISMA search had, and in one review the better tool recovered only 2 of 32. Those were 2023-era tools, but it is a good reason to keep the reproducible search running. So I get two emails, and together they miss less than either alone. It is the same hybrid logic I teach for literature reviews:
An always-on agent adds value only in the urgent tier, flagging the trial the day it posts. For everything else, pick the lightest tool that fits. 5. A simple rule: Do, Digest, Ping, AskPut every task in one of four lanes.
Keep the Do lane small. The list of tasks you can leave to AI unchecked is still short, because the models still make mistakes. Spam filtering belongs there. Receipt filing does too. A manuscript decision does not. Setting up each lane is ordinary delegation: what you want done, where the agent's authority ends, what done looks like, and what to check before calling it finished. The Ask lane also covers what still breaks. Your booking email says the hotel was $1,240. The folio says $1,185 after a refund. No agent has a clean answer yet for two sources that disagree, and OpenAI itself says Dots can still make mistakes. Context cuts both ways. An agent that sees only your work email builds an incomplete reimbursement folder. The more it can reach, the more useful it gets, and the more deliberately you need to decide what it should reach. Patient data stays out of any tool your institution has not approved. 6. Where open models fit: the agent in a siloMy agent is connected to my personal Gmail, not my institutional Microsoft email. That is the right call. Work email holds grant drafts, reviewer correspondence, and messages that brush against patient care, and none of that belongs in a consumer app my institution has not vetted. But it caps what an agent can do for my actual job. Most of my reimbursement paperwork might live in my work email. The way out may be an agent that never leaves your computer. Open-weight models are models anyone can download and run on their own hardware, and they are no longer far behind. Since January 2026, the best open-weight models have trailed the frontier by about four months on average, with Chinese labs such as Moonshot (Kimi), MiniMax, and DeepSeek leading the open pack. Smaller models now fit on a desk: a single consumer graphics card can run models that match the frontier of 6 to 12 months earlier. The agent software exists too. OpenClaw, the open-source agent Meta reportedly modeled Muse on, can run entirely on local models through Ollama. One distinction matters with Chinese models. Running the open weights on your own machine keeps your data on your own machine. Using DeepSeek's own app is a different thing: its privacy policy says data is stored on servers in China. Download the weights. Definitely skip the hosted chatbot. This is not ready for most researchers yet. NYU Shanghai's IT team warns that OpenClaw can pose serious security risks when misconfigured and is meant for technical users. A local model also needs a capable machine, and your institution still decides what touches work email. But the gap is closing fast. I expect a personal agent running on our own computers, completely in a silo, reading the institutional inbox without sending a byte anywhere. That is the version that will file the work receipts too. 7. Start with one quiet jobYou do not need to hand an agent your whole academic life. Start with one task in each of two lanes.
Have you tried an always-on agent or a scheduled task in your research yet? Reply and tell me which job you handed off first. I read every response, and the best examples will make it into a future post. Top Papers on AI in research this week
Top Papers on AI in education this week
The post Your always “ON” AI research agents are here. And why you want them to work like a message board, not Slack appeared first on Rising Researcher Academy. |