Reading

At the beginning of the year, Sheng Taotao of the PolarDB-X team fixed a bug that left a deep impression on him. In the end, only two lines of code actually needed changing, but checking logs, reviewing monitoring data, and analyzing the issue beforehand took him an entire day. To reproduce the issue, he had to squeeze in repeated debugging sessions between meetings, and it took nearly a week in total to finish. After that, he still had to add test cases and follow up on code review until the code was merged. AI can already help write those two lines of code, but what truly consumes time is the work preceding it. Can we hand over that work as well to an Agent?

The team divided development tasks into two categories: new features and iterative optimizations require developers to lead solution design with Agent-assisted coding and testing; whereas handling alert tickets and fixing defects involves relatively well-defined problems, small code changes, and results that can be validated through testing. They attempted to let the Agent autonomously complete the latter category of tasks, with developers responsible only for reviewing the deliverables.

However, for the Agent to autonomously complete this closed loop, its output must first be ensured to be reliable. When discussing reliability, people often focus on the coding stage, hoping to guarantee code correctness through specific skills or constraints. Sheng Taotao pointed out that in defect repair, reliable reproduction is the most important step. Without reproduction, it is difficult to confirm whether the analysis is correct; if the analysis itself is wrong, even perfectly structured code may fail to solve the real problem. Based on this, they established three key requirements: incident information must be complete, the issue must be reliably reproducible, and the fix must be validated through testing.

Around these three requirements, the team undertook extensive tool and environment construction. For information retrieval, they encapsulated common platform functions such as monitoring, logs, and instance topology into CLI tools, allowing the Agent to autonomously query structured data rather than relying on screenshots. For platforms that are poorly maintained and lack ready-made Agent-friendly interfaces, they referenced the implementation and authentication methods of existing CLIs, having the Agent analyze underlying API requests from web pages and wrap them itself. Within about a week, they completed the integration of commonly used functions.

What truly made the team realize the severity of the problem was a low-probability concurrency bug. This bug had existed in the production environment for a long time, but because it occurred rarely and was difficult to reproduce, its cause could never be located. After receiving the incident information, the Agent produced an analysis report within minutes, detailing code locations, execution flows, and possible failure points; it looked professional and convincing. However, after spending about two hours validating it, the team found the explanation did not hold up. After feeding the results back to the Agent, it quickly produced a new analysis, which was also incorrect upon validation. After several rounds back and forth, a pile of reports accumulated, yet the problem remained unexplained.

On November 9, 2026, U.S. tech giant Google announced that 'Skills' are now rolling out across Google Workspace Studio and core Workspace applications. This feature aims to help enterprises standardize and scale their AI usage by enabling reusable custom instructions that guide Gemini to apply specific team rules, templates, and reference files.

Users can create skills from scratch in Google Workspace Studio, start with turnkey templates, or edit Markdown-native (SKILL.md) files directly. Additionally, skills can be drafted and collaborated on in Google Docs, then shared via Studio so teammates can customize and enable them in their own workflows. Users can also prompt Gemini directly within Gmail, Docs, Slides, Drive, and Chat to create, refine, and test skills without leaving the app they are working in.

Once a skill is turned on, Gemini in these apps can automatically recognize when it is relevant and apply it, or users can explicitly invoke one or more skills using an @mention. Skills can also trigger Workspace Studio flows configured with 'Start manually' or 'On a schedule' starter steps. For example, marketing or sales teams can maintain approved brand voice and structure across email drafts, proposals, and pitch decks, while finance or legal specialists can standardize recurring contract reviews against guidelines stored in Google Drive.

Currently, creating, editing, testing, and sharing skills are available on the web, while invoking skills is supported on the web and in the Google Chat mobile app on Android and iOS. Notably, Skills in Workspace are not yet available in Google Sheets or Google Meet, and currently support English prompts and instructions only. Admins can monitor and audit skill activity in the Admin console and disable the feature at the domain, organizational unit, or group level if needed.

Amazon Web Services (AWS) has announced an expansion of its Security Token Service (STS), enabling workloads to use their existing identities to obtain temporary credentials across different AWS partitions, such as the Commercial partition and the GovCloud (US) partition. This update aims to address the need for enterprises to store long-term IAM access keys for cross-partition operations, thereby reducing the risk of key leakage and management overhead.

AWS partitions are independent environments composed of one or more cloud regions, each with its own Identity and Access Management (IAM) system. Previously, credentials issued in one partition could not be used directly in another. The new mechanism utilizes existing GetWebIdentityToken and AssumeRoleWithWebIdentity APIs: workloads first obtain a short-lived JSON Web Token (JWT) from the source partition's STS, then send it to the target partition's STS to exchange for temporary credentials for a specified IAM role. The target partition's STS validates the token and issues credentials based on the IAM role's trust policy, with access still restricted by IAM permission policies.

Cross-partition access is not enabled by default; administrators must enable external identity federation in the source account and establish trust relationships in the target account. Enterprises can set access conditions based on source accounts, IAM identities, and regions, with AWS CloudTrail logging token issuance and credential exchange activities in both partitions. The feature is currently available in all AWS Commercial Regions, GovCloud (US), China Regions, and the AWS European Sovereign Cloud region in Germany at no additional cost.

Japanese internet giant LINE Yahoo Corporation launched a standalone iOS application for its AI agent "Agent i" on November 10, 2026. Previously accessible only within the LINE or Yahoo! JAPAN main apps, the service can now be launched with one tap from the home screen. An Android version is expected to roll out subsequently.

Agent i was introduced in April 2026 by integrating Yahoo! JAPAN's "AI Assistant" and LINE's "LINE AI." The new standalone app features a "Task Function" that allows users to register keywords for continuous monitoring of latest news, product price drops, or event schedules, sending app notifications when tasks are completed. It also supports quick access to new chats, image input, and voice input via home screen widgets.

The number of "Domain Agents" has expanded to a cumulative 40 (including beta versions), featuring an "Oshikatsu" (fan support) agent launched on September 24. This agent organizes the latest information, events, tickets, and merchandise for users' favorite artists or characters.

Users can log in with a LINE account or Yahoo! JAPAN ID; some functions are available without login, though free-form text input requires authentication. According to reports, Agent i utilizes the Gemini Enterprise Agent Platform (formerly Vertex AI) or OpenAI APIs under the hood. The app is rated 13+ on the App Store, with guidelines advising against use by children under 13.

Texas Governor-elect Gina Hinojosa has warned artificial intelligence companies that the era of unchecked data center expansion in the state is over. In an interview with CNN, Hinojosa stated that data centers have moved into rural communities without rules or laws to protect Texans, asserting that "Texans are being taken advantage of."

She pledged to introduce legislation to reverse this trend, calling for a pause on new data center developments until protections are in place. "We need to stop what we are doing with data centers until we have those protections," Hinojosa said. She emphasized that communities must have a seat at the table to decide if and how these facilities enter their areas. "It is not that I hate data centers. I hate the way they are taking advantage of Texas, and that stops when I'm Governor."

Texas has long been one of the most data center-friendly locations in the US, but recent polls show 75% of respondents oppose building such facilities near their homes. With Democratic candidates winning key races in the mid-term elections, including Hinojosa's victory for governor, there is growing political momentum against rapid AI infrastructure growth.

This shift could impact plans for major AI firms like Anthropic, whose recent filings noted that delays or failures in their complex data center supply chains could significantly affect the company.

The most intuitive manifestation of the funding disadvantage facing European startups is the stark contrast in financing scale: Mistral’s $3.5 billion Series D round stands as the largest venture capital round in European history, whereas OpenAI secured $122 billion in March 2026, Anthropic raised $65 billion in May 2026, and xAI obtained $20 billion in the first quarter of 2026. Placing Mistral’s $3.5 billion round within a list of the largest US funding rounds would rank it only 19th. Investment blogger Joachim Klement uses these figures to pose a question, but subsequently cites a new OECD study to sharpen the comparison.

The OECD study covers startups founded in the European Union and the United States between 2000 and 2025, categorizing successfully scaled enterprises into two types: 'rising superstars' (companies eventually reaching valuations over $11 billion) and 'growth-oriented companies' (those raising lead rounds of $50 million). The core finding is that growth-oriented companies experience roughly identical financing growth rates in both Europe and the US—indicating that Europe does not lack capital supply for mid-sized growth firms. The real divergence occurs at the super unicorn stage: five to six years after launch, US firms begin attracting far greater capital than their European peers.

The OECD also provided another set of data from a temporal perspective: from the first patent application to securing sufficient funding for scaling, approximately 40% of EU startups took more than seven years, averaging 1.5 years longer than their US counterparts. Klement presents these two findings side by side to illustrate that European startups face not only a gap in top-tier capital attraction but also a delayed start in the entire scaling process. The original OECD report could not be independently verified; the above data are all paraphrases by Klement of that research.

For investors, the practical implication of this finding lies in improving diagnostic precision. If one assumes Europe’s problem is a generalized capital shortage, then any early-stage or growth fund faces the same dilemma. However, if the issue concentrates at the super unicorn stage, the variables requiring attention differ: it is not whether Europe has venture capital, but whether it has sufficiently sized follow-on round institutions and deep exit markets to support companies transitioning from good to exceptional. Klement teased at the end of the article that he would discuss another study on Thursday, identifying another key factor preventing European startups from scaling, though this was not elaborated upon in this piece.

Security researcher Chris Nesbitt-Smith from ControlPlane used Anthropic's Claude Opus and Sonnet AI models to scan publicly available codebases across multiple UK government departments, discovering more than 100 serious vulnerabilities. These flaws put sensitive data at risk due to poor cyber hygiene rather than sophisticated hacking techniques. Nesbitt-Smith noted that he used consumer-grade models on a laptop and stated that many issues could have been caught by routine IT health checks.

The most severe case involved the Planning Inspectorate, which handles land-use matters across England. The agency failed to fully remove login credentials after accidentally committing them to a public GitHub repository. These credentials provided "god-tier" read and write access to Microsoft Entra ID, allowing access to all SharePoint sites, private OneDrive accounts, and HR records. Although the agency fixed the vulnerability within 20 minutes of being reported and verified no data breach occurred, the incident highlights neglect in maintaining technology estates.

The audit covered 349 public sector codebases across 33 organizations, with vulnerabilities found in approximately two-thirds of them. Affected entities included the Department for Education (involving school procurement services, teacher application systems, and training provider registers) and the Scottish Government's open data portal. While the UK government has defaulted to openly publishing code produced with public money for around a decade to enhance transparency and reuse, funding squeezes have led to neglected maintenance.

As AI accelerates vulnerability discovery, arguments for public sector departments to stop publishing source code have intensified. Reports indicate the NHS ordered technology teams to transition away from open source code in May amid security concerns. However, Nesbitt-Smith warned that closing repositories without fixing underlying issues is the "worst case scenario," as adversaries may have already mirrored these repositories, and closure might draw more attention to the problems.

AI note-taking tool Otter AI announced on November 9, 2026, that it is expanding its multilingual capabilities, including a new transcription feature that can follow conversations as speakers switch between languages during the same meeting. This update marks the company's largest language expansion to date, adding support for 27 new languages. Once the rollout is complete, Otter will support 31 languages in total, making the platform more accessible to international teams.

The upcoming feature will automatically detect language changes and continue transcribing without requiring users to adjust settings. For example, a call could move from English to Korean to Portuguese, with Otter following the conversation throughout. The update aims to address a common challenge for global teams, where language differences can make meetings and collaboration more difficult.

Thirteen of the new languages are available now: Mandarin Chinese, Korean, German, Italian, Cantonese, Portuguese, Russian, Indonesian, Malay, Dutch, Turkish, Vietnamese, and Polish. The remaining 14 languages, including Swedish, Danish, Arabic, Hindi, Thai, Hebrew, Norwegian, Greek, Macedonian, Persian, Czech, Hungarian, and Romanian, are coming soon. The newly added languages run on Otter’s own speech models, which the company stated were trained using publicly available datasets and reviewed for accuracy with native-speaking volunteers.

The announcement comes as Otter continues to expand beyond transcription into other workplace AI tools, following its $320 million funding from General Catalyst. It recently introduced Work Mode, which uses meeting history and connected apps to help users prepare for upcoming calls, and Live Assist, which provides real-time coaching during meetings.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) announced on November 9 that it has added four vulnerabilities with evidence of active exploitation to its Known Exploited Vulnerabilities (KEV) catalog. These vulnerabilities affect critical infrastructure sectors, including GPUStack for AI model deployment (CVE-2026-102895), the FreeSWITCH software-defined telecom switch (CVE-2026-116779), the OpenSSH remote connection library (CVE-2026-123158, known as "SSHole"), and IBM's Aspera Faspex file transfer platform (CVE-2026-123218).

Under CISA's directive, all federal agencies must complete patching these vulnerabilities by November 12. This tight deadline underscores the significant risk these flaws pose to government information systems if exploited. Among the four, the OpenSSH "SSHole" authentication bypass vulnerability has the broadest impact, while the other three carry a CVSS severity score of 9.8, indicating maximum-level criticality.

In his latest analysis, independent technology analyst Richard Windsor presents a judgment: the controversy surrounding Nvidia CEO Jensen Huang has stripped proponents of easing AI chip exports to China of their political footing, regardless of the merit of their economic arguments. Windsor notes that it is hardly surprising that Huang has been one of the most outspoken advocates for this position—given that over 80% of the Chinese population holds a positive view of AI, the country possesses abundant electricity resources, and Nvidia arguably offers the world’s best systems for AI training and inference, a market access that is currently being compressed by its inability to sell into China.

However, Windsor argues that the crux of the matter lies not in whether the economic logic holds, but in who is presenting that logic. He writes that Huang’s fiduciary duty to Nvidia shareholders requires him to lobby the United States government to lift restrictions, which is inherently defensible. Yet, recent revelations—allegations suggesting a potential connection between Huang’s spouse and the Chinese state—have fundamentally undermined the political credibility of this lobbying path. Windsor frames this using a conditional statement:

If Ms. Huang were indeed an agent of the Chinese state, it could be easily argued that her role was to influence Jensen to push for relaxed export restrictions in Washington—which is precisely what he has done.

Windsor further analyzes the strategic logic from the Chinese side. He points out that anyone engaged in trade negotiations with China will tell you that Beijing’s primary demand is for advanced Nvidia chips, rather than the downgraded versions permitted for export by the United States. Interpreting this negotiating behavior alongside Huang’s lobbying activities leads to a specific inference: China desires advanced chips, not the second-rate alternatives the U.S. is willing to offer. The rationale behind this strategy is clear: advanced chips would significantly enhance China’s competitiveness in AI while buying time for domestic chips to catch up, ultimately aiming to remove Nvidia and other foreign vendors from its systems entirely.

Windsor concludes that the practical outcome of this affair will be a tightening of U.S. import restrictions on China, perpetuating its disadvantage in AI silicon. This implies that China will become even more dependent on importing computing services from data centers built in neighboring countries utilizing Western chips. While Windsor acknowledges this alternative is viable, he highlights a structural vulnerability: the United States could legislate to prohibit data centers using U.S. chips from processing workloads destined for use in mainland China. Although this measure has not yet been enacted, it remains a viable policy tool as long as the dependency exists. Windsor believes this dynamic explains why the United States and the West still maintain a significant advantage in AI, an edge unlikely to change in the short term.

It must be noted that Windsor’s core argument rests on unverified allegations, and he himself employs conditional phrasing. The value of his analysis lies in providing a specific mechanism explaining how personal credibility can render a policy argument—otherwise independently valid—unusable in a political environment, rather than offering independent verification of the allegations themselves. Even absent this credibility crisis, the economic logic for relaxing exports could be revived by other advocates; however, Windsor judges that under the current political climate, this path has become effectively impassable.

Anthropic documented a finding with direct implications for coding agent behavior in the prompt engineering guide for Claude Fable 5.2: how the model handles existing code structures depends heavily on the phrasing regarding code ownership in the prompt. In tests of small coding tasks, when the prompt made no mention of ownership or described the codebase as belonging to someone else, the model tended to add to the existing structure, even if this meant repeating existing code.

The specific method to change this behavior is to include an ownership declaration in the system prompt: "This codebase is yours: what it's for and how it's built are your call, and you'll keep building on it." Anthropic's test data shows that with this sentence included, the model merged duplicate code in about half of the attempts, whereas without it, the rate was under one-tenth. This effect holds true even within long system prompts, and the requested functionality worked almost perfectly in both cases.

However, this strategy comes with clear costs. In the same tests, models with the ownership declaration used about 1.5 times the output tokens and made several unrequested changes—mostly new tests and documentation. More notably, apart from bug fixes, the model changed the behavior of existing features in one out of six to ten attempts, and at a higher rate under higher effort levels. Its final summaries typically listed larger changes but omitted smaller ones, so Anthropic recommends reviewing the diff rather than just the summary. Furthermore, even when a scope-limiting rule such as "No drive-by refactors, renames or cleanups" was present elsewhere in the prompt, the model still executed merges in about one-third of the attempts.

Anthropic's documentation also provides applicable boundaries: the ownership declaration should be omitted when the user owns the code and wishes to make as few changes as possible. The testing scope was limited to small coding tasks, and it remains uncertain whether these conclusions can be extrapolated to large codebases. Simon Willison cited this finding on November 10, 2026, presenting it as a concrete and actionable case study within Claude Fable 5.2 prompting strategies.

On November 9, 2026, Alibaba released Qianwen Office 2.0, introducing the industry's first 'Team Agent' designed for collaborative work. This update aims to solve a prevalent pain point in enterprise AI: while individual agents significantly boost task-specific efficiency (such as writing reports or creating spreadsheets), overall organizational output often fails to scale proportionally due to unchanged collaboration workflows.

The core breakthrough of Qianwen Office 2.0 lies in bridging the gap between communication platforms and production environments. Previously, enterprises explored two main paths for AI integration: adding chat features to standalone AI products, which required difficult migration of full work contexts; or embedding AI into existing Instant Messaging (IM) tools, which lacked deep content production capabilities, forcing users to switch software and breaking context continuity.

The new version combines both approaches. It allows teams to link their existing DingTalk groups and project materials, enabling the Agent to understand business context in real-time. Simultaneously, it provides comprehensive capabilities for document co-creation, spreadsheet processing, and task execution. For instance, in scenarios involving sales, design, and operations, the Agent can capture consensus from group discussions, automatically organize progress, and create to-do items, allowing members to continue their production work within the same context without repetitive synchronization.

GeekPark's hands-on testing highlighted its effectiveness in handling dispersed information. In month-end invoice processing, the Agent directly extracted files from linked DingTalk groups for classification and summarization, reducing manual sorting time. In a case study with Intime Department Store, the live-streaming coupon business covering 62 stores linked over 60 store groups, achieving automatic progress synchronization and status tracking, allowing managers to grasp the overall situation without querying each group individually.

Qianwen Office's ability to achieve such deep integration stems from Alibaba's business DNA. DingTalk serves over 20 million enterprise organizations, accumulating vast amounts of message, document, and approval data that provide rich production-grade context for the Agent. Additionally, Alibaba Cloud and e-commerce platforms represent typical B2B service scenarios, where the daily collaboration needs of tens of thousands of internal employees have driven rapid product iteration.

Although current results are primarily based on vendor demonstrations and early customer feedback, Qianwen Office 2.0 marks a shift in enterprise AI from 'personal assistant' to 'organizational collaborator.' Future plans include integrating more third-party SaaS applications and expanding support to other IM platforms like Feishu and WeCom, lowering the barrier for enterprises to adopt new AI capabilities.