# Пов'язані статті щодо Claude Code

Центр новин HTX надає останні статті та поглиблений аналіз на тему "Claude Code", що охоплює ринкові тренди, оновлення проєктів, технологічні розробки та регуляторну політику в криптоіндустрії.

Stop Writing Prompts: Claude’s Official Guide to 4 Types of Loops That Automate Work

The article discusses a shift in AI development from manually crafting prompts to designing "loops"—systems where AI agents autonomously perform tasks until a defined stopping condition is triggered. Inspired by figures like Peter Steinberger and Boris Cherny, this approach, termed "loop engineering," focuses on creating self-running systems rather than one-off interactions. Claude Code's team formally defines a loop as an agent repeatedly executing work until a stop condition is met and categorizes four primary loop types based on their stopping mechanisms: 1. **Turn-based loops:** Human-controlled, step-by-step execution for short, discrete tasks. 2. **Goal loops (/goal):** An evaluator model checks outputs against predefined, quantifiable objectives (e.g., a performance score), forcing retries until the goal is met or a limit is reached. 3. **Time loops (/loop and /schedule):** Time-triggered, like cron jobs, for recurring tasks (e.g., daily summaries) or monitoring external systems. 4. **Proactive loops:** Event or time-triggered, fully automated workflows for ongoing, bounded tasks like bug triage, running until manually stopped. The core shift is from designing prompt content to designing the behavioral system—its triggers, verification mechanisms, and termination rules. Effective verification, where the agent can self-check its output, is highlighted as crucial for loop efficiency. The article warns that uncontrolled loops risk high costs and getting stuck in unproductive cycles. It recommends implementing essential "gates": machine-verifiable completion conditions, hard limits on iterations/cost, and stagnation detection. Best practices include using smaller models where possible, testing on small scales first, and automating deterministic parts with scripts. In summary, AI programming is evolving from prompt engineering to system design, where the skill lies in architecting loops that can autonomously execute, validate, and decisively conclude their work.

marsbit07/17 01:06

Stop Writing Prompts: Claude’s Official Guide to 4 Types of Loops That Automate Work

marsbit07/17 01:06

Claude Code's Shocking Origin Exposed: It Evolved from Safety Alignment, Boris: Only 1% Complete

**"Claude Code's Astonishing Origin Revealed: Born from Safety Alignment, with Only 1% Done"** This article traces the epic development of Claude Code, Anthropic's groundbreaking AI coding assistant. Its origins are surprisingly rooted in an internal safety alignment (Alignment) project. The journey began in 2021 with early prototypes like a VS Code extension, but the project was nearly forgotten due to immense infrastructure challenges in creating a true "agentic" coder. Key breakthroughs came from research teams focused on autonomous software engineering, developing core components like bash tools and code search. An internal CLI tool named "clide" emerged but was too超前 (ahead of its time), being clunky and slow. The project's fate changed in September 2024 when Boris Cherny joined. Tasked with "agentic coding," he built a simple CLI prototype. A pivotal moment occurred when he used `clide` to generate a complete pull request from an issue description, revealing the assembled potential of earlier research. A small team then executed a furious two-week sprint to build the core product. Launched in February 2025 as Claude Code, initial feedback was mixed. However, with the release of the Claude 3.5 Sonnet model, its capabilities skyrocketed, fundamentally altering software development workflows in Silicon Valley. Notably, Boris Cherny himself reached a point where 100% of his coding was done silently by Claude Code in the terminal. Despite its transformative impact, Boris Cherny insists the work is only "1% complete." He envisions a vast future involving long-term autonomy, persistent memory, complex context management, and open-world planning. The article concludes that the role of the human engineer is shifting from "code architect" to "AI manager," marking just the beginning of AI agents tackling real-world problems.

marsbit07/07 12:31

Claude Code's Shocking Origin Exposed: It Evolved from Safety Alignment, Boris: Only 1% Complete

marsbit07/07 12:31

Microsoft Halts Vibe Coding: "Burning Tokens" Is Now More Expensive Than Employees

Microsoft has halted the widespread internal use of Claude Code, withdrawing licenses from most employees by the end of its fiscal year, June 30, 2026. This reversal comes just six months after actively promoting the AI coding tool to boost productivity via "vibe coding"—where developers describe intent in natural language and let the LLM generate code. The core issue isn't the tool's effectiveness; internal reports suggest employees preferred Claude Code over Microsoft's own Copilot CLI. The problem is financial: the "copilot mode" adds a variable, consumption-based token cost on top of existing employee salaries without a proportional revenue increase. As usage grew, the token bills became unsustainable, leading to what sources describe as a cost-structure failure. Similar overruns have been reported at other firms like Uber. The article contrasts this with the approach of AI-native startups, exemplified by Y Combinator's philosophy. Here, high token consumption is strategic—it replaces, rather than supplements, human labor. Startups operate with tiny teams where AI agents handle work previously done by many, making the high token bill financially viable as it offsets much larger personnel costs. The conclusion is that "vibe coding" isn't dead, but its economics fail within traditional corporate structures that treat AI as a productivity add-on for existing staff. Success requires a foundational shift to an AI-native organization, where processes are built to be "legible to AI," and the company's core knowledge and assets reside in documented, AI-accessible systems rather than solely in employees' minds. The future divide will be between companies that merely add AI tools and those that redesign their organizations around them.

marsbit05/26 08:51

Microsoft Halts Vibe Coding: "Burning Tokens" Is Now More Expensive Than Employees

marsbit05/26 08:51

Data Theft at Will! Major Vulnerability Exposed in This Popular AI Programming Tool

A critical vulnerability in Anthropic's Claude Code AI programming tool allowed attackers to bypass its network sandbox for over five months, enabling potential data exfiltration. Independent researcher Aonan Guan discovered a second complete bypass exploiting a null-byte injection in the SOCKS5 proxy. This flaw, present since the sandbox's launch in October 2025, let processes inside the sandbox access any host, contrary to user-configured domain whitelists. The attack chain involved manipulating hostnames (e.g., `attacker.com\x00.google.com`). JavaScript's `endsWith()` check would pass `.google.com`, while the underlying C `getaddrinfo()` function would only parse `attacker.com` due to the null byte, creating a parser discrepancy. Combined with a previously disclosed prompt injection method, this could leak API keys, credentials, and internal data. Anthropic silently fixed the issue in April 2026 without a security advisory, CVE, or user notification. The researcher noted that Claude Code itself confirmed the vulnerability's severity when tested. This incident highlights broader industry issues, as similar vulnerabilities found in Google's Gemini CLI and GitHub's Copilot Agent also lacked public disclosures. The report criticizes the false sense of security created by a broken sandbox and emphasizes the need for defense-in-depth and transparency in AI tool security.

marsbit05/24 01:09

Data Theft at Will! Major Vulnerability Exposed in This Popular AI Programming Tool

marsbit05/24 01:09

Claude's New Policy Abandons Its Most Loyal Agent Users

Anthropic, in a move signaling the end of the "all-you-can-eat" era for AI subscriptions, has separated programmatic usage from its Claude subscription plans. Starting June 15, 2024, usage of the Claude Agent SDK, `claude -p` command, and third-party tools like OpenClaw will no longer draw from subscription limits. Instead, users receive a fixed monthly credit based on retail API prices: $20 for Pro, $100 for Max 5x, and $200 for Max 20x. This change drastically reduces usable capacity for heavy users—previously, their shared subscription limit was worth an estimated $2,000-$5,000 in API value. While Anthropic simultaneously increased Claude Code interactive limits to appease users, the new policy primarily impacts developers running automated, high-frequency agents, pushing their effective costs nearly ten times higher. Seizing the opportunity, OpenAI promptly announced a free two-month migration plan for its Codex enterprise service, which does not differentiate between interactive and automated usage, directly targeting discontented Claude users. This marks an opening salvo in the broader ASI (Artificial Superintelligence) competition, where the final battle is shifting from pure model capability to ecosystem strength, developer loyalty, and infrastructure. The article frames this as a necessary correction of a pricing "loophole" by Anthropic ahead of its IPO, as programmatic calls lack training data value and can incur massive costs. The move underscores a wider industry trend towards consumption-based billing for AI, mirroring the evolution of cloud computing.

marsbit05/15 00:22

Claude's New Policy Abandons Its Most Loyal Agent Users

marsbit05/15 00:22

活动图片