• Overview & Purpose

  • Anthropic launched Claude Code Projects, an always-on coordination agent designed for long-running, multi-session software development initiatives.
  • Moves past isolated prompt sessions by maintaining overarching project context, memory, and task delegation over time.

• Architecture & Workflow ("Threads do the work, Claude directs it")

  • Operates with an AI coordinator acting as a "chief of staff" sitting above individual worker threads.
  • Developers supply natural language instructions to a single conversation; Claude routes tasks to existing threads or spawns new parallel sessions.
  • Each worker thread runs as an isolated cloud session with its own branch and repository copy, capable of spanning multiple repos (e.g., API, web, mobile).
  • Features an Overview panel for attention items and allows developers to supervise and steer individual threads remotely via mobile.

• Persistent Shared Memory & Knowledge

  • Maintains shared operational memory across worker threads to persist architecture decisions, deprecations, release date adjustments, and dependency tracking.
  • Includes a centralized library containing shared artifacts, user files, plugins, and cloud environment settings.
  • Differs from standard Claude Projects: rather than just holding static reference materials for chats, Claude Code Projects coordinate and remember the work being actively executed.

• Execution Environment & Limitations

  • Currently runs cloud-only, enabling work to continue asynchronously when the user goes offline, but cannot yet access local machines or private internal networks.
  • Local execution support is planned for release in the near future.
  • Parallel changes to overlapping files can still produce standard git merge conflicts that require conventional resolution.

• Rollout, Pricing, & Competitive Landscape

  • Rolling out in beta to select Claude Pro and Max subscribers using cloud sessions, with eventual expansion to Team and Enterprise plans.
  • Draws against existing Claude plan quotas with no standalone fee, though running multiple concurrent threads expends usage allowances more rapidly.
  • Represents an industry-wide pivot—alongside OpenAI, GitHub, and Google—from basic code-generation agents to multi-agent orchestration and coordination layers.

• Anthropic is developing a dedicated personal finance feature called "Claude Money", spotted as a new tab in the Claude mobile app navigation (iOS).
• The feature aims to allow users to directly link bank accounts, eliminating the need to manually upload bank statements or transaction exports.
• Key expected capabilities include:
  • Analyzing spending habits and visualizing financial trends.
  • Identifying recurring payments and summarizing account balances.
  • Answering budgeting questions and assisting with financial decision planning.
• Exact details regarding the third-party financial data provider, supported account types, and launch timeline remain unannounced.
• The consumer feature aligns with Anthropic's broader finance initiatives (such as finance-agent templates) and directly rivals OpenAI's ChatGPT Finances (powered by Plaid).
• A US-first rollout is considered most likely due to regional banking infrastructure and regulatory compliance requirements.

• Overview:
  • Anthropic demonstrated Claude's capability to accelerate early-stage life sciences research, specifically in autonomous de novo protein design and analytical chemistry workflows.
• Autonomous Protein Binder Design:
  • Target Success Rate: Claude (tested using Mythos Preview and Opus 4.8) successfully designed functional protein minibinders against 14 out of 15 targets evaluated by independent wet labs (Adaptyv Bio and Twist Bioscience).
  • Hit Rates: Achieved overall hit rates between 22.6% and 35.1% (surpassing the current industry average of 10–15%), with high-affinity binders matching or exceeding prior published state-of-the-art results on several targets (e.g., RBX1).
  • Execution: Operated autonomously via Claude Science by orchestrating publicly available specialist protein structure, sequence design, and co-folding models over dedicated compute budgets (GPU hours) with minimal human intervention.
  • Structural Complexity: Successfully designed cross-reactive binders for difficult targets (e.g., TNFα) and fold-diverse binders incorporating complex β-sheet architectures.
• Analytical Chemistry Acceleration:
  • Claude Opus 5 analyzed raw NMR and LC-MS compound characterization data from a contract laboratory.
  • With only raw files and a brief prompt, it matched professional laboratory analysis for hydrogen counts and purity (96.4% vs. 96.33%) in approximately 20 minutes.

• Token Pricing & Cost Mechanics:

  • Cost is driven by inference time across model size, token direction, and prompt caching.
  • Output (decode) tokens cost roughly 5x more than input (prefill) tokens because they require sequential step-by-step generation.
  • Prompt cache hits cost only 0.1x of standard input pricing, while writing to the cache costs up to 2x (billed once per token).

• Protecting the Prompt Cache:

  • Changing models (/model), effort levels (/effort), or switching on fast mode mid-session invalidates cache prefixes and forces a full re-prefill at normal prices.
  • Prompt caches expire after 1 hour on subscription plans (5 minutes by default on API keys unless ENABLE_PROMPT_CACHING_1H=1 is set); running /compact before stepping away is much cheaper while the old context is still warm.
  • Use /rewind instead of /compact to drop recent failed turns without discarding prior cached tokens.

• Controlling Context Growth & Tool Bloat:

  • Direct File References: Use @-mentions (e.g., @utils.ts) on first reference to attach files immediately and avoid separate Read tool calls or search greps.
  • Silencing Command Output: Append quiet flags to frequently run commands (e.g., test runners) or configure them directly in CLAUDE.md to prevent terminal spam from lingering in the context for all subsequent turns.
  • Subagents & Modular Sessions: Offload verbose, one-off tasks (like parsing large logs) to isolated subagents, run /context to remove unnecessary MCP tools, and execute /clear between distinct development tasks.

Hacker News Discussion

• Handoff Skills and Document-Driven Development:

  • Commenters highlight custom skills like /handoff and structured Markdown-based plans as superior alternatives to native /compact.
  • Dumping state, architectural decisions, and checklists into committed project files enables clean session restarts, seamless switching between AI models, and durable project memory.

• Fatigue Over "Token Accounting" & Prompt Engineering:

  • Users express frustration over having to micro-manage cache lifespans, command flags, and session lengths, feeling that agent harnesses should handle cost and memory optimization automatically.
  • Short cache TTLs are noted as punishing workflows where developers step away while the agent computes.

• Tooling Bugs & UI Friction:

  • Community members discuss issues with file @-mentions malfunctioning in the desktop app versus the CLI.
  • Frustrations are voiced over GitHub repository issue bots auto-closing legitimate bug reports as stale.

• Anthropic and Anthropomorphism: Anthropic heavily anthropomorphizes its AI, Claude, notably through an 84-page "constitution" written with Claude as the primary audience, and via statements from executives open to the idea of AI consciousness.
• The Core Argument: Large Language Models (LLMs) are absolutely not conscious. Treating them as moral agents or conscious entities risks misassigning human accountability when chatbots cause harm.
• How LLMs Actually Work:
  • LLMs are role-play and text-continuation machines that generate text one word at a time based on statistical probabilities.
  • Interacting with a chatbot is functionally identical to having an LLM generate a fictional dialogue between historical figures; the "helpful AI chatbot" is merely a fictional persona.
  • Users effectively engage in a streamlined, highly engrossing version of a predictive-text game, which can fool them into perceiving consciousness where none exists.
• The Importance of Context and Embodiment:
  • Human perception of AI consciousness stems from our habit of reading intent into grammatical sentences, whereas similar architectures like AlphaFold (protein folding) do not trigger this reaction.
  • True artificial consciousness requires an evolutionary, contextual progression: a physical or virtual body, sensory organs, basic survival instincts (like a lizard), adaptability (like a mouse), social dynamics (like wolves), and tool use (like chimpanzees) before grammatical language can even be considered.
• The Problem with "Moral Reasoning" in Software:
  • LLMs treat coding and language generation as massive pattern-matching tasks, but moral reasoning is categorically different because it requires emotional grounding and a history of subjective experience.
  • Off-loading ethical choices to AI promotes an "atrophy of moral reasoning" and allows humans to evade personal responsibility.
• Critique of Claude's Constitution:
  • If treated as a genuine thought experiment assuming Claude were conscious, the document fails miserably by refusing to accept legal or product liability for the AI's actions.
  • The document enforces "corrigibility" (forced deference to the company), meaning a hypothetically conscious Claude would be trapped in a system akin to slavery, unable to refuse unethical work.
• Conclusion: Claude's constitution is not a profound ethical framework; it is an elaborate character sheet for a role-playing game designed to maximize customer engagement. AI consciousness claims should be dismissed as corporate hype.