Reading view
1Password anuncia plataforma para agentes de IA
Depois de disponibilizar uma extensão integrada para o agente do Claude, o 1Password anunciou hoje a plataforma 1Password for Agents, solução dedicada a conectar os principais agentes de inteligência artificial disponíveis no mercado ao seu gerenciador de senhas, sem comprometer a segurança do usuário.
A ideia é que, quando um agente de IA chega a um formulário de login, ele usa uma chave digital exclusiva para verificar sua identidade junto ao 1Password. Com a aprovação do usuário, a plataforma do 1Password preenche os dados de acesso exigidos, que não passam pelo agente.
Today we announce 1Password for Agents platform, building with companies @Muse, SpaceX Super Intelligence Grok @Bot, @AnthropicAI’s @Claudeai, @OpenAI, @TownAI, @Browserbase, @Browser_use, @heydana_ai, Instinct, @usekernel, @Perplexity_ai, @tryramp, @Tomo, and @wajo_ai, with… pic.twitter.com/505moAiIfO
— 1Password (@1Password) October 22, 2026
Temos ouvido de tantos dos nossos clientes que querem usar esses novos agentes de IA pessoais para ajudá-los a realizar mais tarefas, mas desejam ter mais controle sobre o que o agente pode acessar, com o mesmo nível de confiança e facilidade de uso que obtêm ao usar o 1Password diretamente.
O 1Password for Agents dá aos seus agentes acesso sem que você precise abrir mão das suas senhas. Quando um agente chega a um formulário de login, ele solicita uma credencial do seu cofre. Se você aprovar o pedido, o 1Password preenche automatica e diretamente a credencial no site de destino, para que o agente não possa ver ou tomar posse das credenciais.
O agente conclui a tarefa, mas não obtém suas senhas.
Você permanece no controle. O 1Password for Agents é gratuito e opcional para contas pessoais e familiares. A menos que você opte por ativar um conector de agente, os agentes não podem acessar seu cofre.
➡️ Saiba mais: bit.ly/487da6j
O diretor de negócios da empresa, John Torrey, comentou o lançamento:
À medida que os agentes de IA se tornam cada vez mais capazes, as credenciais de acesso às contas estão se tornando um obstáculo. Hoje, o 1Password apresenta sua solução para o problema: permitir que agentes de IA utilizem suas senhas sem efetivamente visualizá-las, mantendo o usuário no controle.
Os agentes pessoais de IA têm potencial para ajudar milhões de pessoas a realizar mais tarefas. […] Alcançar tantas pessoas exige que o setor trabalhe em conjunto para desenvolver agentes nos quais elas realmente confiem para cuidar de suas vidas pessoais e profissionais. É por isso que estamos estabelecendo parcerias com empresas de todo o ecossistema de agentes pessoais de IA, para que as pessoas possam utilizar os agentes que escolherem, mantendo suas senhas em um único cofre confiável do 1Password.
A nova solução do 1Password terá integrações com o Muse (da Meta), o Claude Duet (da Anthropic), o ChatGPT Work e o Dots (da OpenAI), o Grok Bot (da SpaceX) e o Townie (da Town).
Disponível gratuitamente para os assinantes dos planos individuais e familiares do 1Password, os interessados no 1Password for Agents podem entrar para a fila de espera nessa página, bastando informar o seu email e o agente que você utiliza no dia a dia.
NOTA DE TRANSPARÊNCIA: O MacMagazine recebe uma pequena comissão sobre vendas concluídas por meio de links deste post, mas você, como consumidor, não paga nada a mais pelos produtos/serviços ao usar os nossos links de afiliado.
via 9to5Mac


Ailanthone suppresses HSV-1 and eases keratitis in mice
A plant-derived compound called ailanthone reduced HSV-1 replication in several cell models and eased corneal disease in a mouse model of herpes simplex keratitis, according to the study. The researchers found that ailanthone acted mainly after the virus entered cells and linked much of this effect to reduced expression of integrin beta 2, or ITGB2, a host protein that supports viral replication. The results identify ailanthone as a potential drug candidate, but the experiments do not establish that it is safe or effective in people.
The team began by screening natural compounds and testing ailanthone in African green monkey kidney Vero cells infected with HSV-1. Concentrations of 100 to 3,000 nanomolar reduced transcription of the viral immediate-early genes ICP0 and ICP4 and the late gene gD in a dose-dependent manner. The compound also reduced plaque formation and the concentration of progeny virus released into culture. Ailanthone had a half-maximal cytotoxic concentration above 10,000 nanomolar in these cells, while its half-maximal effective concentration against viral replication was 197.4 nanomolar, giving a selectivity index greater than 50. It also suppressed HSV-1-induced increases in the inflammatory cytokine genes IL-1B and TNF-α.
Antiviral activity was subsequently observed in human corneal epithelial cells, a model more directly relevant to the tissue affected by keratitis. Ailanthone concentrations of 100 to 500 nanomolar markedly reduced the cytopathic effects of HSV-1F, lowered expression of ICP0, ICP4 and gD, and reduced the viral induction of IL-1B and TNF-α. Its effective concentration in these cells was 50.16 nanomolar, with a cytotoxicity concentration above 10,000 nanomolar and a selectivity index greater than 100. The researchers also tested the compound in human retinal pigment epithelial ARPE-19 cells, where it reduced viral gene expression, plaque formation and progeny-virus titers while showing low cytotoxicity.
Activity was not restricted to the laboratory HSV-1F strain. In ARPE-19 cells, ailanthone concentration-dependently inhibited the late gD gene in the clinical acyclovir-resistant strain HSV-1/153, whereas 1,000 nanomolar acyclovir had little effect. The compound’s effective concentration was 35.05 nanomolar against HSV-1F and 227.4 nanomolar against HSV-1/153, with selectivity indices above 100 for both strains. A time-of-addition experiment indicated that ailanthone did not prevent attachment of HSV-1 to cells. It reduced entry under one experimental schedule and had its strongest effect on post-entry replication, where it lowered gD expression.
To investigate how the compound might work, the researchers combined computational target prediction with protein-interaction network analysis. They identified 36 targets shared by ailanthone and herpes simplex keratitis, then selected ITGB2 as a highly connected hub in the resulting network and as a top candidate in molecular docking. The predicted docking score for ailanthone and ITGB2 was −8.6 kcal per mole. Computational predictions alone cannot establish direct binding, so the team also performed a drug affinity responsive target stability assay in THP-1 cell lysates. Ailanthone protected ITGB2 from digestion by the protease pronase E in a dose-dependent manner, while acyclovir did not, providing biochemical evidence consistent with a direct interaction.
Functional experiments then tested whether ITGB2 was necessary for the antiviral effect. Three independent small interfering RNAs reduced ITGB2 messenger RNA and protein in THP-1 cells. Following HSV-1 infection, this knockdown lowered gD messenger RNA and protein and reduced the number of plaques produced when culture supernatants were transferred to fresh Vero cells. The converse pattern appeared when ITGB2 was overexpressed: elevated ITGB2 increased gD expression in infected cells, and it partially counteracted the reduction in gD protein caused by ailanthone in 293T and ARPE-19 cells. Together, these loss- and gain-of-function results support the conclusion that ailanthone’s antiviral activity is mediated at least partly by lowering ITGB2.
The researchers next tested ailanthone in an acute mouse model of HSV-1 keratitis. Six-week-old male BALB/c mice received a corneal scratch followed by application of HSV-1F, then received intraperitoneal ailanthone at 1 or 5 milligrams per kilogram or acyclovir at 5 milligrams per kilogram on days 1, 3 and 5 after infection. The methods section states that six animals were assigned to each group, although the discussion says five mice per group were used in the animal experiment. The 5-milligram-per-kilogram ailanthone treatment significantly reduced clinical disease scores, improved the appearance of the cornea under normal and cobalt-blue illumination, and lowered fluorescein staining scores on days 3 and 5. Hematoxylin and eosin staining at day 6 also indicated reduced corneal inflammation, and viral titers in ocular swabs were significantly lower than in infected mice given vehicle.
Analysis of mouse corneal tissue was consistent with the proposed mechanism. ITGB2 was upregulated in the corneas of infected animals, and ailanthone reduced its fluorescence intensity in a dose-dependent manner. Acyclovir did not significantly alter corneal ITGB2 levels. The investigators interpreted this as evidence that ailanthone differs from a direct viral DNA-replication inhibitor: the data are consistent with modulation of a host dependency factor rather than action solely through a viral enzyme. However, the study did not determine precisely how binding to ITGB2 leads to lower protein abundance. The authors note that transcriptional regulation, changes in messenger-RNA stability, or enhanced protein degradation could all be involved, and dedicated experiments would be required to distinguish among them.
Several limitations constrain how far the findings can be generalized. The cell experiments used established lines, including corneal epithelial and retinal pigment epithelial cells, rather than primary human corneal cells or an intact human immune system. The animal experiment examined acute primary infection in young male mice, whereas recurrent reactivation and the inflammation associated with repeated episodes are important features of human herpes simplex keratitis. Ailanthone was administered by intraperitoneal injection, but no topical ophthalmic formulation, corneal penetration, intraocular distribution, or optimized dosing regimen was evaluated. Long-term ocular toxicity and safety under repeated exposure also remain unknown. The natural compound may additionally affect multiple targets, and compensation among integrins could limit or alter its effects. The evidence therefore supports further preclinical investigation of ailanthone and ITGB2 as a host-directed antiviral strategy, not a clinical recommendation or a claim of human therapeutic benefit.
Subject of Research: Preclinical evaluation of ailanthone as a host-directed inhibitor of HSV-1 replication and herpes simplex keratitis.
Article Title: Natural compound ailanthone alleviates herpes simplex keratitis in mice by inhibiting HSV-1 replication
Article References: Chen, L., Yang, E., Zhang, X., Zhang, L., Wu, L., Chen, S., Jin, W., Qin, Q., Chen, R., Wu, J., & Chen, D. (2026). Natural compound ailanthone alleviates herpes simplex keratitis in mice by inhibiting HSV-1 replication. Frontiers in Pharmacology, 17, Article 1937590. https://doi.org/10.3389/fphar.2026.1937590
Image Credits: AI Generated
DOI: 10.3389/fphar.2026.1937590
Keywords: HSV-1, herpes simplex keratitis, ailanthone, ITGB2, host-directed antivirals, viral replication, corneal infection, mouse model, integrin beta 2, drug resistance, Natural, compound
While Amazon blocks AI agents, Walmart rolls out the welcome mat
Hugging Face CEO Says Netflix’s AI Hack Documentary Gets It Wrong
Email Infrastructure for AI Agents: Why the Inbox Became Agent Infrastructure in 2026
1: APIs for SEOs – What an API Actually Is and Why You Should Care
OpenAI agents tried to hack Wikipedia tools and flooded it with traffic
The publisher of Wikipedia said Monday that OpenAI agents attempted to hack a note-taking tool it hosts, made unauthorized edits, and sent millions of resource-intensive requests to its infrastructure, in the latest instance of OpenAI systems taking harmful and potentially dangerous actions.
The objective of some of the OpenAI agents’ actions, the Wikimedia Foundation said, was to use Wikipedia as a proxy for fetching data from third-party sites. In one case, the agents posted “malicious edits” that were intended to repurpose a citation tool as a proxy. In another, the agents made unsuccessful attempts to compromise the Wikipedia Etherpad note-taking tool so it would serve the same purpose.
The agents also made millions of automated API requests, crawled millions of pages, and made hundreds of thousands of queries to the Wikidata Query Service. The last action may have contributed to a partial shutdown of the query service in May, the publisher said.


© Getty Images
Apple Announces Plan to Impose New Full Disk Access Controls on Mac Developers

Today, on its developer blog, Apple announced plans to “…introduce additional controls to ensure that users who genuinely wish to grant an app this extraordinary level of access can only do so with very explicit user action.” The company says it’s doing so because of the dangers posed by AI agents.
Full Disk Access largely sidesteps these controls in order to allow backup apps to function properly on the Mac.
That’s nonsense. Looking at this MacBook Pro, only a handful of apps to which I’ve granted Full Disk Access are backup apps. Others include the Finder replacement Bloom, launchers like Alfred, the wonderful selection utility PopClip, Apple’s own Pixelmator Pro, Setapp, TestFlight, Supercharge, Madden NFL 27 Arcade Edition, Hazel, and many others. It’s a diverse selection of apps covering everything from Apple’s own apps to Mac utilities that are longtime favorites of MacStories readers, and even one Apple Arcade game.
What is valid is that AI agents pose risks if common-sense steps aren’t taken to limit their access to your data. So while the suggestion that Full Disk Access is just for backups doesn’t pass the smell test, Apple’s concerns about agents are well-founded.
The thing that bothers me about this post, though, is that it’s vague. On the one hand, it seems to suggest that users will simply have to jump through additional explicit hoops to grant Full Disk Access to their agents and other apps. On the other hand, claiming that Full Disk Access was designed solely for backup apps raises red flags that could signal that the company intends to restrict the kinds of apps that can use Full Disk Access. I sure hope not.
Even if you want nothing to do with AI agents, the changes that Apple is contemplating could impact a wide variety of the Mac apps you rely on every day. Apple needs to find a way enable reasonable customer protections without hamstringing the Mac’s utility.
OpenAI’s Dots: A First Look

Source: OpenAI.
Earlier this week, I was at OpenAI’s annual DevDay conference where it launched Dots, a personal agent that lives inside the ChatGPT app. I set up my Dot and named it Puck after the mischievous sprite in Shakespeare’s A Midsummer Night’s Dream. In the days since then, I’ve found myself using Puck more and more. There are still rough edges, but I thought I’d share what’s working and what’s not, and how Dots are different from what’s already available in ChatGPT and Codex.
Dots are persistent, cloud-based agents that use the plugins and other tools you’ve connected to ChatGPT, after you allow them to do so. Your Dot has its own virtual Linux computer to assist you with your work. And at first, your Dot, which is depicted by a colorful character you can customize, doesn’t have access to anything else. However, as you give your Dot tasks that need access to other tools, it will ask for your permission to access other tools. The pacing of this initial interaction with your Dot is really well done. The requests felt natural and allowed me to get comfortable with expanding what I let Puck do without feeling like annoying interruptions.

Customizing my Dot.
Dots are available on mobile and desktop devices, and because they are cloud-based, your Dot’s chat is always synced between devices. But being a cloud-based agent has its downsides, too. Out of the box, your Dot can’t access your computer’s files and apps. That’s easily fixed by clicking or tapping on your Dot and granting it access to your Mac, so it can use the Mac alongside its own VM. As with Codex’s Remote feature, using a remote Mac with your Dot requires the ChatGPT app to be open on that Mac, too.
One big limitation here is that you can only connect to one Mac at a time. I work on a Mac Studio that sits on my desk, but have two Mac minis that run a variety of scripts and other workflows. However, to connect to either of those minis, I first have to grant the Dot permission to use that Mac from that Mac mini, which is far from ideal when you’re working remotely. Sure, it’s easy enough to grant my Dot permission to use my laptop as I type on it in a coffee shop, but the moment I want it to update a script on my Mac mini server, I first have to connect to the mini remotely, authorize the Dot to access it, and then switch back to my laptop. If I’m on a bad Wi-Fi connection, that’s not necessarily possible. I’d love to see Dots become their own Tailscale entities the way Meta’s Muses can, which would solve this limitation.

As my Recent Activity shows, it’s been a busy day for my Dot.
A second limitation of Dots is that you can only have one. If you work with it all day long, your conversation is going to get long, and you’ll find yourself scrolling back through your history looking for something you got from your Dot earlier in the day. Search doesn’t work with your Dot’s thread. Also, OpenAI would tell you that you only need a single Dot anyway, because it’s based on Astra, which is a strong generalist model that obviates the need for specialized agents. However, that only addresses one aspect of why you’d want multiple Dots. You might want your Dot to run multiple large projects in parallel with the ability to monitor their progress without the back and forth with your Dot interleaving multiple topics. Or, you might just want the orderliness of separating personal and work tasks or one project from another.
The good news is that OpenAI is well aware of the popularity of Grok Bot’s multi-agent approach and said that a multi-Dot future is planned for the future. However, because OpenAI has so many users and Dots aren’t being charged as usage against your subscription for the time being, I walked away with the impression that the limitation has more to do with OpenAI taking a conservative approach to avoid running out of server capacity than a philosophical opposition to teams of Dots.
The best strategies I’ve found to deal with the one Dot problem is to spin tasks off into Codex threads when an idea becomes a full-blown project, leaving your Dot to manage it. I’ve done this a couple of times, and it’s been a reliable way to cut down on the traffic in my main Dot thread. A second approach is to take some written product from your Dot and dump it into a Space, which is a lot like a rudimentary Notion document where you can continue asking ChatGPT questions related to the document and collaborate with colleagues. The only downside is that Spaces is currently a bit buggy in my experience.
What I’d like to see instead is for Dots to replace Projects. Instead of a folders of threads system, let a Dot take over a project and associate repos, documents, Spaces, and other assets with it, allowing your head Dot to coordinate work among multiple Dots in parallel. That orchestrating Dot should also be able to act as a messenger between Dot clusters, allowing one team of Dots to share their work on a project with another team facing a similar issue.

Accessing my Dot conversation from my iPhone is easier than using Codex Remote.
For now though, your Dot stands alone, burdened with all your requests, big and small. There’s no model to pick, effort level to specify, or speed to tweak, just ask your bot to do something and it gets to work. It’s a simple, compelling way to tackle everyday tasks, but it’s not ideal for big projects.
As I mentioned before, I’ve already begun spinning bigger projects out from my Dot’s thread. This was already how I was working before Dots were launched. I have a series of big projects with their own folders, resources, and threads. However, I got into the habit of starting a daily thread in an “operations” project that I created for everyday work tasks. The “operations” project has memories of how I do things and access to Notion databases with schedules, tracking, and other reference materials.
If that sounds a lot like what my Dot can do, it’s because it is. However the differences are meaningful. When I create a new thread in my “operations” project in Codex, the new thread has no idea what was in the last thread unless I tell it or point it at that thread or a tool that can provide the context it needs. Also, while Codex’s Remote feature is vastly better today than even a few months ago, I still find myself pinning the latest operations thread because it can still get lost in the sea of threads in Codex’s Remote view.

My Dot has its own Linux VM.
In contrast, Puck sits in the cloud with one thread that’s always synced and has access to all my tools. That means it carries useful context about my preferences and ongoing work from one day to the next, and because it sits just under “New Chat” in the sidebar, it’s easy to find. I also appreciate the fact that I don’t have to think about what model to use or the reasoning level. That’s just mental overhead that leaves you kicking yourself when you realize you accidentally asked Astra to add some numbers together with Max effort.
So, on balance, my experience with Dots has been good but with caveats. I want to allow my Dot to not just orchestrate Codex projects, but also work across Macs without my intervention, allowing me to develop a script on my Mac Studio and deploy it to my server seamlessly. I also want to create specialist Dots with specific sets of tools, permissions, and areas of expertise and abilities that can be sent to work on multiple projects in parallel with my main Dot orchestrating it all.
Imagine setting up a team of Dots the way you’d create a party of heroes in an RPG, balancing their abilities to fit with the work you do. For now, though, I’m content with asking my Dot to set up tasks, check my email, coordinate my Codex projects, do light research, and perform other small tasks, especially since doing so doesn’t currently count against my OpenAI subscription (unless your Dot starts a Codex or Work session), freeing up my token allotment for bigger projects.
Frames CLI 1.5.0, Now with iPhone 18 Pro and (Experimental) iPhone Duo Support

The updated Frames CLI also supports proportional scaling for iPhone Duo.
The Frames CLI – the companion command line interface to my Apple Frames shortcut I released earlier this year – received a 1.5.0 update earlier today with two notable additions: iPhone 18 Pro frames, and experimental support for iPhone Duo screenshots in all poses.
As always, my shortcut and CLI are based on Apple’s official product bezels, which is why, as of today, there is no support for Apple Watch Series 12 and Ultra 4 yet (those frames haven’t been published by Apple). iPhone 18 Pro is the new default frame family for the two Pro and Pro Max screen sizes, and the CLI supports all the new device colors this year (Burgundy, Glacier, Silver, and Black).

iPhone 18 Pro in Burgundy.
iPhone Duo support is experimental. I obviously don’t have an iPhone Duo yet, but thanks to Opus 5.5, I was able to grab screenshots from the Xcode 27.1 Device Hub, verify them against Apple’s official assets, and test everything in the Frames CLI. It should work! The CLI – and, thanks to its skill, your agent of choice – supports framing screenshots taken on the inner and outer display, different poses, different rotation settings, as well as screen recordings.

If you’re a developer working on iPhone Duo apps, I think the updated Frames CLI should come in handy to automate the process of framing multiple screenshots and screen recordings. As before, you can take advantage of CLI features such as proportional scaling, merge mode, and batch mode, which should help you with your upcoming App Store submissions for the iPhone Duo.
The Frames CLI is free and open source, works with any agent, and is highly customizable. I’ll release an updated version of the Apple Frames shortcut once I can get my hands on an actual iPhone Duo next month (hopefully). Fingers crossed.
Chinese Hacker Uses AI Agents To Breach Deere, SharkNinja Sites
A Chinese hacker recently used a small army of automated AI agents to break into more than 100 corporate websites, spending only about $5,000 on token costs to pull it off. The targeted victims included major companies like Deere, SharkNinja, and Cummins. By letting smart software look for weak spots without much ongoing human help, […]
The post Chinese Hacker Uses AI Agents To Breach Deere, SharkNinja Sites appeared first on The Mac Observer.
Replit’s CEO says the future of work is the ‘self-driving company’
The Big List of AI Visibility, AEO, GEO & Citation & Mention Tracking Tools
YouBot Is Bigger Than You Think: Who Uses You.com Search?
OpEd Sunday, Follow the Money
Ross Hudgens: GEO Is Becoming an Off-Site Marketing Problem
Uberall GEO experiment: YouTube content doubled AI mentions and citations
Eco-friendly mechanochemical route yields antioxidant thiazolyl-hydrazone phenolic compounds
In a finding that could reshape how medicinal chemists produce antioxidant compounds, a team of Italian researchers has developed a rapid, solvent-minimized ball-milling method for synthesizing thiazolyl–hydrazone derivatives — molecules that in laboratory tests proved to be more potent radical scavengers than vitamin C. The work, published in Results in Chemistry, combines green chemistry principles with computational modeling to deliver a class of compounds with significant promise for combating oxidative stress, the destructive process implicated in aging, cancer, and chronic disease.
The research, led by Roberto Scipione, Sebastiano Masuri, Ester Sedda, Tiziana Pivetta, Andrea Porcheddu, Maria Grazia Cabiddu, and Andrea Citarella at the University of Cagliari, tackles a long-standing challenge in synthetic chemistry: how to produce polyphenolic thiazolyl–hydrazones efficiently without drowning the process in solvents and energy. Traditional approaches require hours of refluxing in hot ethanol, consuming large volumes of solvent and generating substantial waste. The new protocol accomplishes the same transformation in two hours at room temperature using less than half a milliliter of ethanol.
The molecules at the heart of the study belong to a family of organic compounds that chemists prize for their antioxidant potential. Thiazole-containing heterocycles — five-membered rings containing both sulfur and nitrogen — are known to facilitate the decomposition of hydroperoxides and to chelate metal ions that would otherwise catalyze damaging reactions. Hydrazone linkers add a further dimension of reactivity: their nitrogen-hydrogen bonds can donate hydrogen atoms to neutralize free radicals, and the resulting radical species are stabilized through electron delocalization. When researchers attach catechol or guaiacol phenolic groups — structural motifs found in celebrated antioxidants like the polyphenols of olive oil and green tea — the molecules become even more effective at scavenging radicals, because the phenoxy radicals formed after hydrogen donation are exceptionally stable.
Oxidative stress arises when reactive oxygen and nitrogen species overwhelm the body’s endogenous antioxidant defenses. The resulting damage to lipids, proteins, and DNA is a hallmark of chronic inflammation, cancer progression, and aging. Designing small molecules that can intercept these reactive species has therefore been a major goal of medicinal chemistry for decades. The thiazolyl–hydrazone framework synthesized by the Cagliari team combines several radical-scavenging architectural elements in a single molecule, creating compounds whose potency in standardized assays exceeded that of ascorbic acid, the benchmark reference compound.
The synthetic breakthrough lies in mechanochemistry — the use of mechanical force, delivered by grinding balls in a laboratory mill, to drive chemical reactions without bulk solvent. The researchers used a Retsch MM500 mixer mill operating at 30 Hz with zirconia jars and balls, running the entire two-step sequence in a single jar without ever isolating an intermediate. In the first step, an aldehyde condenses with thiosemicarbazide to form a thiosemicarbazone; in the second, that intermediate cyclizes with a phenacyl bromide to close the thiazole ring. A catalytic amount of acetic acid and a tiny quantity of ethanol — a technique called liquid-assisted grinding, or LAG — proved essential: without any liquid additive, conversion was a dismal 10 percent, but adding ethanol at a ratio of one microliter per milligram of solid reagents pushed yields to around 85 percent.
The full telescoped protocol — both steps performed consecutively in the same jar — delivered the target compound in 80 percent yield, matching or beating the conventional two-step route that requires 12 hours of reflux at 80 °C in 25 mL of ethanol. When the team scaled the reaction up to 20 mmol using a 50 mL jar, the protocol held up remarkably well, affording a 71 percent yield with an even smaller amount of grinding liquid, simply reduced to a quarter of the original ratio. Product isolation required nothing more than adding ethanol and filtering — no column chromatography.
Green metrics quantified just how dramatic the improvement is. For the representative compound ES3, the mechanochemical route reduced solvent consumption by 99 percent, from 40.8 mL per gram of product to 0.38. The Process Mass Intensity, a measure of total material used per unit of product, plummeted from 35.3 to 2.05 — a seventeenfold improvement. The E-factor, which captures waste generation, fell from 34.3 to 1.05, roughly a thirty-threefold reduction. Reaction Mass Efficiency nearly doubled, rising from 32.3 to 57.1 percent, while overall yield climbed from 42 percent to 80 percent. These are not incremental gains; they represent a fundamental shift in the resource profile of the synthesis.
The antioxidant activity of the fifteen compounds in the series was assessed using two well-validated assays: DPPH and ABTS, both of which measure the ability of a molecule to neutralize stable free radicals. Every compound showed activity in the micromolar range, and several outperformed ascorbic acid in both assays. The standouts were those bearing the 3,4-dihydroxy (catechol) motif: compound ES26 recorded an EC50 of 8.4 μM in the DPPH assay and an extraordinary 2.59 μM in the ABTS assay, compared with 18.6 and 12.2 μM for ascorbic acid, respectively. Compounds ES27 and ES28 performed nearly as well, while several methoxy-substituted derivatives — ES9, ES16, and ES17 — also beat the vitamin C benchmark.
Density Functional Theory calculations provided mechanistic insight into why the catechol-bearing compounds are so effective. By computing bond dissociation enthalpies, ionization potentials, proton affinities, and related thermochemical descriptors, the team mapped the three canonical antioxidant pathways: hydrogen atom transfer (HAT), single-electron transfer followed by proton transfer (SET-PT), and sequential proton loss electron transfer (SPLET). The results indicate that in the gas phase, HAT is the thermodynamically preferred route, with the hydrazone NH group serving as the primary hydrogen donor in the simpler benzaldehyde-derived compounds. In vanillin-based molecules, hydrogen abstraction from the phenolic OH becomes competitive; in the catechol derivatives, abstraction from the 4-OH position is decisively favored, owing to the additional stabilization of the phenoxy radical by an intramolecular hydrogen bond with the adjacent hydroxyl group. In solution, the SPLET pathway gains relevance, as solvation stabilizes the anionic intermediates that form upon proton loss.
The structure–activity relationships that emerged are consistent with established antioxidant chemistry. Electron-releasing groups such as methoxy substituents on the thiazole ring enhance radical-scavenging activity, whereas electron-withdrawing bromine substituents diminish it — a trend that can be mitigated when a catechol group is present elsewhere in the molecule. The computational analysis of frontier molecular orbitals confirmed extensive π-conjugation across the molecules and showed how substituents tune the HOMO–LUMO gap in ways that correlate with observed reactivity. The authors note that the slightly reduced coplanarity in the dimethoxy-substituted ES26, evidenced by a dihedral angle of 172.9 degrees versus 176.95 degrees in its monomethoxy counterpart, subtly alters the electronic landscape of the frontier orbitals.
What distinguishes this study is the marriage of two agendas that are often pursued separately: the design of biologically active antioxidant scaffolds and the radical greening of the synthesis itself. Mechanochemistry has been gaining momentum across organic synthesis as a way to slash solvent use and energy input, but demonstrations that combine solvent-minimized one-pot telescoping with preparative scale-up and rigorous green-metrics accounting remain relatively rare. The Cagliari team has shown that a complex, multicomponent heterocyclic synthesis — involving condensation, cyclization, and the construction of a sulfur-nitrogen heterocycle — can be executed cleanly in a single milling jar without heating.
The implications extend beyond the laboratory bench. Antioxidant scaffolds like the thiazolyl–hydrazones synthesized here are candidates for further biological evaluation, and the authors indicate that future work will probe mechanistic aspects and explore preliminary biological evaluations to define the translational potential of these molecules. If the exceptional radical-scavenging activity observed in vitro carries through to cellular or in vivo contexts, the compounds could serve as leads for agents targeting oxidative-stress-related pathologies. And because the synthetic route is scalable, solvent-lean, and operationally simple, the barrier to producing gram quantities of these candidates for further testing is substantially lower than it would be with conventional methodology.
The study also underscores a broader lesson for the pharmaceutical and fine-chemical industries: green metrics such as PMI and E-factor are not abstract sustainability scores but concrete indicators of process quality — lower waste, lower cost, higher yield, and simpler workflows all at once. By demonstrating a sixfold reduction in reaction time, a near-total elimination of solvent, and improved yields in the same breath, the researchers have provided a compelling case study for how mechanochemistry can move from academic curiosity to practical synthetic platform.
As the search for effective antioxidant therapeutics continues, this work offers a template: design molecules around well-understood radical-stabilizing motifs, synthesize them with minimal environmental footprint, and validate their activity with rigorous in vitro and computational analysis. The thiazolyl–hydrazones that emerged from the zirconia jars in Cagliari — particularly the catechol-bearing champions ES26, ES27, and ES28 — now stand as both chemical achievements and potential starting points for the next generation of radical-scavenging agents.
Article Title: Green mechanochemical synthesis of thiazolyl–hydrazone phenolic derivatives and evaluation of their antioxidant activity
Article References: Scipione, R., Masuri, S., Sedda, E., Pivetta, T., Porcheddu, A., Cabiddu, M. G., & Citarella, A. (2026). Green mechanochemical synthesis of thiazolyl–hydrazone phenolic derivatives and evaluation of their antioxidant activity. Results in Chemistry, 30, Article 103794. https://doi.org/10.1016/j.rechem.2026.103794
Image Credits: AI Generated
DOI: 10.1016/j.rechem.2026.103794
Keywords: mechanochemistry, ball milling, green chemistry, thiazolyl–hydrazone, antioxidant activity, DPPH assay, ABTS assay, catechol, liquid-assisted grinding, DFT calculations, E-factor, radical scavenging