Claude Opus 4.8 launches: what is new in Anthropic's strongest model?

Imagine having an AI assistant that is incredibly smart but forgets everything between sessions and cannot check the quality of its own work. To solve this problem, developers created a protective management layer around AI models called an agent harness. This is what enables AI agents to complete complex, multi-step tasks autonomously without requiring constant human intervention. What is an agent harness? Think of an AI model as a brilliant new employee with no long-term memory and zero familiarity with the workplace. They can solve complex problems in seconds but will just as easily forget what they were working on, or accidentally send a confidential document to the wrong client. In that scenario, an agent harness acts as the experienced manager sitting right beside them, keeping things on track. Put simply, an agent harness is the software layer wrapping around an AI model that handles all administrative and logistical work so the model itself can focus entirely on reasoning and problem-solving. It connects the AI to external tools, maintains a complete record of work across sessions, and verifies results before considering a task done. In practice, an agent harness handles the following: Connecting the AI model to external tools such as web search, email, and calendars Persisting progress across sessions so the AI never has to start from scratch Filtering out irrelevant information and supplying only the data the AI actually needs at each step Monitoring AI actions to prevent dangerous mistakes Logging activity in detail so humans can audit what happened when needed Origin of the term: The concept of "agent harness" was formally named by technology engineer Mitchell Hashimoto in early 2026. Before that, many development teams had built similar systems but had no shared term for this layer of infrastructure. Why do AI agents fail at long-running tasks? The biggest weakness in today's AI models is the complete absence of long-term memory. Every new conversation starts from zero with no recollection of anything that happened before. Imagine hiring an employee who wakes up every morning having forgotten every agreement, every deadline, and every piece of progress from the day before. When Anthropic tested Claude building a complex web application without harness support, the results were consistently disappointing. Two failure modes kept appearing: The AI tried to do everything at once, ran out of working memory midway through, and left the project unfinished. The next session wasted time trying to figure out what had already been done. The AI declared the task complete without actually running the result to verify it worked. Beyond those two core failures, long-horizon tasks expose three additional problems: Context clog: Accumulated conversation history and tool outputs crowd out the original instructions, causing the AI to gradually lose focus on the actual goal Tool misuse: The AI sometimes searches for information that does not exist or submits incorrect inputs to forms, and without anything to stop it, repeats the same error in a loop Total progress loss on failure: Any network error or system crash wipes out whatever was stored in temporary memory, forcing a full restart Stanford research (2023): AI models tend to overlook information buried in the middle of long text, even when that text is not particularly long. This is why feeding too much data to an AI all at once often backfires without a filtering layer in place. How does an agent harness work in practice? An agent harness operates in two distinct phases to keep work flowing continuously without interruption. Setup phase (runs once) The harness prepares the full working environment before the AI begins: building a structured task list, initializing storage, and recording the starting point. Think of it as the manager drawing up a detailed project plan before handing anything off. This phase only needs to happen once. Execution phase (repeats) Each time the AI begins a new session, the harness automatically reloads all saved progress and assigns only the next relevant task. When the AI wants to take an action such as searching for information or sending a notification, the harness checks whether that request is valid, executes it safely, cleans the returned result, and passes it back to the AI. The model never touches external systems directly without going through this control layer first. The four core components of an agent harness For an AI to operate reliably over extended periods, a standard agent harness needs four essential components: External tool gateway: Allows the AI to interact with the real world by reading documents, searching the web, or sending messages. The harness acts as an intermediary, validating every request before execution and ensuring returned results are clean and usable. Layered memory management: Maintains three types of memory serving different needs: short-term working memory for the current session, a task log recording what has been completed and what remains, and a long-term knowledge store that accumulates across multiple projects over time. Intelligent context filter: Summarizes long conversation histories down to key points and supplies only the data relevant to the current step rather than loading everything at once, keeping the AI focused on the right task at the right moment. Safety checker and human approval gate: Automatically verifies results before marking a task as complete. For sensitive actions such as deleting important data or sending bulk emails, the harness pauses and waits for human confirmation before proceeding. Note on accumulated knowledge: If an AI agent's memory is stored entirely within a closed third-party platform, all the knowledge it builds up over time belongs to that platform. Switching to a different system means starting from zero. This is worth thinking through carefully when choosing a long-term AI agent solution. Harness engineering and the secret behind millions of lines of code Harness engineering is the practice of treating every AI failure as a system problem to fix permanently rather than something to retry or ignore. As Mitchell Hashimoto put it: if the agent makes a mistake, redesign the environment so that mistake becomes physically impossible to repeat. In practice, when OpenAI built large software projects with three engineers producing 3.5 pull requests each per day without typing a single line of code, they had set up automatic verification checks after every AI action. When the AI produced something incorrect, the system returned error messages written in a specific structure so the AI immediately understood what needed to change on the next attempt. Every error message became a learning signal, not just a warning. A study presented at ICML 2025 further confirmed that the same AI model equipped with a harness consistently outperformed itself running without one, even with identical training weights and identical prompts. The environment surrounding the AI matters just as much as the model itself. A telling data point: Anthropic's Claude Code has grown past 512,000 lines of code and continues to expand. More capable models do not make the harness simpler. They make it larger, because there is more capability to orchestrate and more failure modes to guard against. When do you actually need an agent harness? For simple one-off tasks like summarizing a document or answering a specific question, calling an AI directly is perfectly fine. But the moment work extends beyond a single conversation, requires memory from a previous session, or involves multiple steps that need to happen in a specific order, a harness becomes necessary. One thing worth reflecting on: the built-in web search in ChatGPT and Gemini is itself a form of harness. When AI automatically looks something up, there is infrastructure behind the scenes making the tool call, processing the result, and feeding clean information back into context. The harness is invisible to the user but indispensable to the system. Agent harness is not a short-term technical trend. It is the answer to fundamental limitations that AI cannot resolve on its own: no long-term memory, finite working context, and a tendency to misuse external tools without guardrails. 4AIVN has also started applying harness to our own workflows — and what we have found is that it does not just help AI finish tasks. It turns AI into a system that learns from failure and gets more reliable over time.

Anthropic has just announced a partnership with SpaceX to access over 220,000 NVIDIA GPUs and will immediately use this new computing power to increase usage limits for both Claude Code and API. Here's what's changing and why it matters to users. Why Did Anthropic Partner with SpaceX? In recent months, Anthropic has continuously signed large-scale computing agreements with Amazon, Google, Microsoft, and NVIDIA. This time, the company has added another unexpected name: SpaceX. According to the announcement on May 6, Anthropic signed an agreement to use the entire computing capacity at SpaceX's Colossus 1 data center, equivalent to over 300 megawatts of power and more than 220,000 NVIDIA GPUs. This entire capacity will be put into use within one month and will directly improve the experience for Claude Pro and Claude Max users. Colossus 1 is SpaceX's AI data center, currently one of the largest GPU clusters in the world. Anthropic is the sole tenant of its entire capacity. Specific Changes to Usage Limits Thanks to the new computing resources, Anthropic has implemented three changes effective immediately from the announcement date Doubling Hourly Claude Code Limits The 5-hour rate limit for Claude Code is doubled for Pro, Max, Team, and Enterprise plans. If you previously could only run 10 complex Claude Code commands, this is now doubled to 20, which will be significantly helpful. However, it's important to note that the weekly limit remains unchanged, so while increasing the 5-hour limit allows for more intensive work in a short period, it might cause you to hit the weekly cap faster. Removing Peak Hour Limits Previously, Claude Code automatically reduced usage limits during peak hours (typically from 9 AM to 3 PM) for Pro and Max accounts. This limit has been completely removed, so users can now use Claude Code at full speed regardless of the time of day. For users who often work in the evening (which coincides with US peak hours), this change is likely to have the most noticeable impact. Significantly Increasing API Limits for Claude Opus Models The API rate limit for Claude Opus models has been significantly increased. Details of the multiplier increase are published by Anthropic in the following table: This change is particularly important for developers building applications on the Claude Code platform Anthropic's Overall Computing Strategy The agreement with SpaceX is not an isolated move. In recent months, Anthropic has built a remarkable infrastructure portfolio: An agreement for up to 5 gigawatts with Amazon, with nearly 1 GW operational before the end of 2026 A 5 GW agreement with Google and Broadcom, expected to be operational from 2027 Strategic partnerships with Microsoft and NVIDIA, including $30 billion in Azure capacity A $50 billion investment in AI infrastructure in the US with Fluidstack And now, over 300 megawatts from SpaceX's Colossus 1 data center Anthropic runs Claude on various hardware platforms — AWS Trainium, Google TPUs, and NVIDIA GPUs — and states that it continues to seek additional computing power sources. Notably, within the framework of the agreement with SpaceX, both parties also expressed interest in developing orbital AI computing capabilities, i.e., placing GPUs on satellites. This is still a very early-stage idea, but if realized, it would be a major turning point for global AI infrastructure. Expanding to International Markets A portion of the expanded computing capacity will be used to serve international enterprise customers, especially in sectors requiring local data storage such as finance, healthcare, and government. The agreement with Amazon also includes additional inference capacity in Asia and Europe. Anthropic also emphasized that it only expands to countries with democratic legal frameworks and secure hardware supply chains, demonstrating a cautious stance amid increasingly fierce geopolitical competition in AI. What Does This Mean for Claude Users in Vietnam? From a practical perspective, the three changes to usage limits directly benefit those who use Claude Code daily — especially programmers and individuals who work continuously with Claude Code. The removal of peak hour limits also means that the experience for users in Vietnam (whose time zone often coincides with peak load periods in the US) will be more stable. In the long term, greater computing power often means the ability to deploy more powerful models at lower costs. This is the foundation for Anthropic to continue competing with OpenAI and Google in the 2026 AI race. Anthropic is Always Evolving Anthropic is seriously investing in infrastructure, and the partnership with SpaceX is the latest step in that strategy. The most immediate result users can feel is that Claude Code will be less restricted, and API speeds will certainly improve. In the long run, the computing race among major AI companies promises many more interesting developments in 2026.

Anthropic had previously introduced Claude to Excel, PowerPoint, and Word, and has now opened the public beta for Outlook. If you've been following Anthropic's release history in recent months, the question is no longer what feature they will launch next, but rather if there is any software they haven't jumped into yet. Claude is now available across all Microsoft Office applications From now on, all paid plan users can install Claude into Microsoft's office suite. Claude for Excel, PowerPoint, and Word have been available for a while, while Claude for Outlook is entering public beta for all paid tiers. The biggest difference compared to other Office AI assistants is that Claude does not act like a chatbot locked in individual apps. Instead, conversation context is maintained seamlessly as you move between applications—from Outlook to Word, then Excel, and on to PowerPoint—without needing to explain yourself from scratch. Claude for Microsoft 365 can be installed via Microsoft AppSource. A single package covers Excel, PowerPoint, and Word, while a separate package is available for Outlook. Administrators can perform centralized deployments from the Microsoft Admin Center. [VIDEO: F6dzjaBCBtU |Claude for Microsoft 365 (Anthropic)|Claude for Microsoft 365 (Anthropic)] What can Claude do in each application? Excel: Far beyond just explaining formulas Claude for Excel can read multi-sheet workbooks, explain formulas with cell-by-cell references, build financial models with live formulas, and update assumptions without breaking dependency structures. Every change is tracked and clearly displayed so users always know which cells Claude used. PowerPoint: Working directly within your slides This is the most notable feature: Claude for PowerPoint reads the native slide structure, detects existing fonts, colors, and layouts, and then generates new content in that exact style. The charts it produces are native PowerPoint charts that are fully editable, not pasted screenshots from elsewhere. Word: Tracked edits and replying to comments Claude for Word works the way editors like: all edits appear as tracked changes, and Claude can reply directly to comment threads, including explaining what it changed and why. Nothing is saved or sent until you accept it. Outlook (Beta): Organizing your inbox with a single command Claude for Outlook categorizes emails into three groups: requires your reply, can be drafted on your behalf, and can be skipped. The drafted emails appear directly in Outlook's compose window, complete with recipients, subject lines, and body text—you just need to review and hit send, which is fully equivalent to what Claude can do with Gmail. Cross-application context: A familiar feature that rarely works in reality Anthropic describes a typical scenario: receiving an email in Outlook, opening the attachment in Word to draft a memo, switching to Excel to perform an analysis, and finally transforming it all into a slide deck in PowerPoint—and of course, Claude remembers all the context across every single step. More importantly, files can be opened side-by-side and changes will sync: adjusting an assumption in Excel will automatically update the numbers in the Word memo and the charts in PowerPoint. Chat history is saved per file, meaning you can close the sidebar, turn off your computer, open it the next day, and continue right where you left off. Claude for Microsoft 365 also supports voice dictation instead of typing. Built for enterprise: Complete control and compliance For enterprise administrators, Anthropic has added configuration capabilities to route all prompts, tool calls, and document references to the organization's own auditing system—helping the security team know exactly what Claude did in each session. The analytics dashboard also breaks down activity by user, application, and day. In terms of routing, organizations can connect Claude via direct accounts or existing cloud platforms like Amazon, Google Cloud, or Microsoft. Microsoft 365 Copilot customers can also access Claude models directly within Excel and PowerPoint. Workflows can be saved as skills and perform consistently across all four applications. Once a process is standardized, the entire team can use it the same way. The software world is chasing Anthropic It is no exaggeration to say that Anthropic is releasing at a speed that startles many competitors. In just the past few months: the Claude Code programming tool has been constantly updated, the integration ecosystem is expanding rapidly, browser and desktop tools have been added, and now, all four Microsoft Office applications are supported at once. Microsoft, which has long placed a massive bet on Copilot with exclusive ChatGPT models, is now opening the door to Claude within its own ecosystem. This speaks volumes about Anthropic's current standing, but the real story will be decided by the users: whether Claude in Excel, Word, Outlook, and PowerPoint will truly shift the office habits of Microsoft 365 users.

Many people still do research manually: opening a dozen tabs, watching videos, reading articles, taking notes in scattered places, and then spending even more time trying to synthesize the result. A long-form post by monokern on X suggests a different pattern: use Claude Code to orchestrate the workflow, NotebookLM to analyze sources, and Obsidian to store long-term memory. Done correctly, this is not just a search session. It becomes an AI workflow that compounds over time. The core idea is practical: Claude Code does not need to do everything inside an expensive context window. It can call tools, run skills, create files, and offload heavy source processing to NotebookLM. The output is then saved back into Obsidian as markdown, giving the next research session better context. According to the original post, the initial setup can be completed in under 30 minutes if the required tools are already available. Why does this stack work? The strength of the workflow is that each tool owns a clear layer. Claude Code acts as the execution engine: it receives plain-language instructions, calls skills, runs commands, manages files, and coordinates the pipeline. Instead of forcing the user to operate each step manually, Claude Code becomes the system operator. NotebookLM is the analysis layer. Google's research tool can read sources, summarize them, generate analysis, flashcards, mindmaps, infographics, or audio overviews. When Claude Code sends source processing to NotebookLM, the user benefits from Google's processing layer rather than spending Claude tokens on every piece of long-form digestion. Obsidian is the memory layer. Every analysis result is saved as markdown in a personal vault. Over time, that vault becomes a structured knowledge base of topics, sources, observations, patterns, and conclusions. Claude Code can read those files later to understand what the user cares about, what formats they prefer, and how they tend to evaluate a topic. Skill Creator turns the workflow into a reusable tool The first major step in the guide is installing Skill Creator inside Claude Code. This layer lets users describe a new capability in natural language, after which Claude Code creates the skill structure, installs it, and makes it available as a reusable command. In other words, instead of rebuilding the research prompt every time, the user packages the workflow as a dedicated skill. The first example is a YouTube search skill. It uses yt-dlp to search videos by query and return metadata such as title, channel, views, duration, upload date, URL, and a views-to-subscribers ratio. For content or market research, this is more useful than a plain list of links because it shows which sources are actually attracting attention. NotebookLM handles the heavy analysis The post proposes connecting Claude Code to NotebookLM through notebooklm-py because NotebookLM does not currently provide an official public API. After installation and Google account authentication, Claude Code can use a custom skill to create a new notebook, add sources such as YouTube URLs, text, or files, and then ask NotebookLM to generate analysis or deliverables. The key point is that NotebookLM is not only a summarizer. In a real research pipeline, it can receive 10 videos on a topic, analyze which frameworks are gaining traction, which ones are overhyped, where the community disagrees, and what content gaps remain uncovered. That processing takes time, but most of the work happens on the NotebookLM side. The full pipeline: one command for a complete research task Once the YouTube search skill and NotebookLM skill exist, the next step is to create a pipeline skill that combines both. The user gives a topic, such as researching AI agent frameworks in 2026, and the pipeline searches for relevant sources, creates a notebook, adds those sources, runs the analysis, and returns the result as markdown. In monokern's example, the pipeline finds 10 video sources, sends them into NotebookLM, generates analysis, creates an infographic, and saves the result into Obsidian. The total processing time is described as around 6 minutes, most of which is NotebookLM processing. The practical value is that the user does not need to open every tab, copy every link, or manually combine the metadata. The final output is more than a chat answer. It includes full analysis, source lists, engagement metrics, trend observations, a visual deliverable, and a markdown file saved into the vault. That is what separates this workflow from a normal chatbot interaction. Obsidian makes the system smarter over time Obsidian is the most interesting part. If the workflow runs only once, it already saves time. But if it runs regularly, every new markdown file makes the personal knowledge base richer. After a month, Claude Code can see recurring topics, the types of insights the user values, and the preferred format for results. The post also highlights the role of the claude.md file inside the vault. This can become a configuration file describing working conventions, analysis style, and output preferences. After several research sessions, the user can ask Claude Code to read recent work and update that file so it better reflects the user's current process. The real value is the structure, not YouTube YouTube is only the data source in the example. The pipeline structure is the valuable part. Users can replace YouTube with academic PDFs, industry reports, public documentation, web pages, local files, transcripts, or Google Drive documents. As long as Claude Code can access the source and pass it into the analysis layer, the operational template stays the same. This opens many practical uses: researching a crypto ecosystem through whitepapers and public documentation, analyzing an emerging technology through conference talks, mapping content gaps in a niche, or tracking market dynamics from public reports. In every case, the same three layers remain: collect sources, analyze them, and store knowledge. What should you watch out for? This workflow is powerful, but it is not for everyone. It assumes the user is comfortable with Claude Code, has an Obsidian vault, can install CLI tools such as yt-dlp, and is willing to use an unofficial library to connect to NotebookLM. Also, because NotebookLM and YouTube can change access patterns, these skills should be treated as maintained tools rather than install-and-forget automation. Still, the underlying idea is important: instead of using AI as a disconnected chat box, turn it into a research system with memory, a pipeline, and the ability to learn from your own work history. For people who regularly analyze markets, technology, or content, this is far more practical than opening 10 tabs and manually stitching everything together.