Artículos Relacionados con Context

El Centro de Noticias de HTX ofrece los artículos más recientes y un análisis profundo sobre "Context", cubriendo tendencias del mercado, actualizaciones de proyectos, desarrollos tecnológicos y políticas regulatorias en la industria de cripto.

AI Competition's New Battlefield: Long-term Memory Becomes the Pain Point, How Users Can Secure Their Own Context Ownership

A new front is emerging in the AI competition: user ownership of long-term memory and context. As AI models like ChatGPT evolve from chat tools into persistent digital assistants that learn user preferences and workflows, a critical question arises: who owns this accumulated "memory"? Currently, this personalized data is siloed within each platform (e.g., OpenAI, Anthropic, Google), creating a fragmented experience when users switch models. The article highlights ZetaChain's strategic pivot from blockchain interoperability to addressing this AI "memory" challenge. Its new focus is on building a "Private Memory Layer" and an "AI Consumer Layer." Through its consumer product Anuma, ZetaChain aims to give users encrypted, portable memory that can be used across different AI models. This system also envisions programmable, auditable permissions for AI agents and a framework where user knowledge can be monetized as shareable assets. Ultimately, ZetaChain's transformation reflects a broader infrastructure shift. The future bottleneck is less about raw model capability and more about continuous context, user-controlled identity, and permission management across multiple collaborating AI agents. The company's ZETA token is being repositioned as an "AI infrastructure token" to facilitate access, payments, and permissions within this proposed ecosystem. The core narrative advocates for returning control of personal context and AI relationships to users, rather than leaving them locked within proprietary platforms.

marsbitHace 23 hora(s)

AI Competition's New Battlefield: Long-term Memory Becomes the Pain Point, How Users Can Secure Their Own Context Ownership

marsbitHace 23 hora(s)

Agentic Design Patterns: A Book That Made Me Re-Understand "What Is an Agent, Really?"

"Agentic Design Patterns" is a 2025 book by Antonio Gullí, a Google engineering director, which offers a systematic framework for AI Agent development through 21 design patterns. A core contribution is the "Four Levels of Agency": Level 0 (bare LLMs) are not true agents. Level 1 agents actively decide when and how to use tools. Level 2 agents engage in strategic planning, context engineering (curating and filtering information), and self-reflection. Level 3 involves multi-agent collaboration with defined communication topologies. The book introduces **Context Engineering** as a superset of prompt engineering, managing four layers of information for the agent: system prompts, external data, implicit context (user history, environment), and feedback loops for automated optimization. A key pattern is **Reflection (Producer-Critic)**, where two distinct agents with different prompts collaborate iteratively—one produces output, the other critiques it—until quality is satisfactory or a max iteration limit is reached. For **Memory**, a three-layer model is proposed: Session (ephemeral conversation context), State (temporary task data), and Memory (persistent, long-term storage). Regarding **Multi-Agent Systems**, the book advises against unnecessary complexity, recommending simple topologies like Supervisor or Peer-to-Peer based on task needs. It emphasizes perfecting a single Level 2 agent before moving to multi-agent setups. The author concludes with three actionable takeaways: 1) Add a Critic agent to existing workflows, 2) Practice Context Engineering beyond simple prompts, and 3) Avoid premature multi-agent complexity; first master a robust single agent. The book provides a practical map, codifying common challenges like reflection, memory, and coordination into reusable patterns, saving developers from reinventing foundational solutions.

链捕手05/25 04:43

Agentic Design Patterns: A Book That Made Me Re-Understand "What Is an Agent, Really?"

链捕手05/25 04:43

How an Anthropic Engineer Saved 300 Million Tokens in a Week: A Claude Code Caching Guide

Anthropic engineers reveal how prompt caching in Claude Code dramatically reduces token consumption. By reusing already-processed context, cached tokens cost only 10% of regular input tokens. The author saved over 300 million tokens in a week, with 91 million cached tokens in a single day counted as roughly 9 million for billing. Caching works via prefix matching across three layers: system (instructions, tools), project (CLAUDE.md, rules), and conversation (chat history). As long as the beginning of a request matches cached content, Claude reuses it instead of reprocessing. Key points for users: - Claude Code's cache TTL is 1 hour (vs. 5 minutes for API/Sub-agents). Avoid pausing a session beyond this. - Switching models (including enabling "Opus plan" mode) breaks cache, forcing a full reprocess. - For task switching, use a clear session handoff instead of letting an old session expire. - Place large documents in Projects, not directly in chat, for better caching. High cache reuse benefits both users (longer sessions) and Anthropic (lower costs). Monitoring cache hit rates is crucial internally. By managing context as an asset and avoiding cache-breaking habits, users can make their Claude Code sessions more efficient and cost-effective.

marsbit05/24 00:36

How an Anthropic Engineer Saved 300 Million Tokens in a Week: A Claude Code Caching Guide

marsbit05/24 00:36

How to Become a Pro Claude User in 30 Days?

"How to Become a Claude Power User in 30 Days" outlines a structured month-long program to transform from a casual user into someone who leverages Claude as a core productivity system. The first week focuses on mastering prompt structure (Role, Context, Task, Format, Constraints), understanding context windows, and setting up foundational Projects and Memory for personalized context. The second week involves building reusable workflows for research, writing (using a two-step outline-first process), and decision-making. The third week shifts to automation: using Claude Cowork for autonomous file tasks, connecting tools like Google Drive and Slack, and setting scheduled automation. The final week is for compounding gains: optimizing all workflows based on feedback, building a personal knowledge repository, teaching the system to a colleague, and designing a complete, ideal "Claude Operating System." By day 31, the user operates with an autonomous assistant that handles routine tasks with deep context, freeing them for high-value creative and strategic work. The core message is that consistent, systematic configuration over 30 days creates a powerful, personalized productivity advantage.

marsbit05/20 08:06

How to Become a Pro Claude User in 30 Days?

marsbit05/20 08:06

Topping GitHub's Trending, the Essential Guide for Claude Code Users

The CLAUDE.md file, trending on GitHub, is a project-level guide for Claude Code designed to dramatically improve its accuracy and efficiency. It addresses key issues like repetitive context explanations, unauthorized code changes, and forgotten decisions across sessions. By placing this plain-text file in a project root, Claude Code reads it automatically at the start of each session. The guide includes rules to eliminate redundant explanations, enforce strict behavioral constraints (e.g., no modifications outside the requested scope without confirmation), and establish a "memory" system using companion files like MEMORY.md and ERRORS.md to log past decisions and failures. It also locks in the project's specific tech stack to prevent inappropriate tool recommendations. Highlighted are four foundational rules from Andrej Karpathy that reportedly increased coding accuracy from 65% to 94%: always ask for clarity first, implement the simplest solution, never touch unrelated code, and explicitly flag uncertainties. The article quantifies significant weekly cost savings for developers and teams by eliminating wasted time on re-explaining context, rolling back unauthorized edits, and re-evaluating previously rejected solutions. The core message is that a small, upfront investment in creating a CLAUDE.md file leads to a more predictable, controlled, and cost-effective AI programming assistant.

marsbit05/18 09:38

Topping GitHub's Trending, the Essential Guide for Claude Code Users

marsbit05/18 09:38

In the AI Era, How to Onboard Without Starting from Scratch

In the AI era, onboarding new employees often resembles a botched relay race baton handoff, where the organization maintains speed while the newcomer starts from zero. The author, after joining Ramp, argues the core problem is a lack of accessible, shared organizational "context"—the collective knowledge from meetings, documents, Slack discussions, and decisions. Instead of relying on slow, manual onboarding or isolated AI tools, the solution is building a continuously updated "company brain." This system acts as a central, AI-native knowledge base that absorbs all company signals. The author describes building a prototype using an Obsidian vault powered by Claude, fed by automated meeting transcripts and notes, and topped with reusable agent "skills." The current enterprise AI approach, deploying specific workflow agents, is likened to the "chatbot era"—useful but disconnected. The real gap is the absence of a shared brain that all agents and employees can access from day one. The future lies in making context layer infrastructure the priority: write context first, then install tools; record every meeting; build the wiki before the dashboard. When new hires, AI agents, and even customers can immediately access this living company brain, the costly "ramp-up" period becomes obsolete. True organizational speed is achieved when maximum velocity and seamless context transfer happen simultaneously.

marsbit05/17 06:03

In the AI Era, How to Onboard Without Starting from Scratch

marsbit05/17 06:03

Your Claude Will Dream Tonight, Don't Disturb It

This article explores the recent phenomenon of AI companies increasingly using anthropomorphic language—like "thinking," "memory," "hallucination," and now "dreaming"—to describe machine learning processes. Focusing on Anthropic's newly announced "Dreaming" feature for its Claude Agent platform, the piece explains that this function is essentially an automated, offline batch processing of an agent's operational logs. It analyzes past task sessions to identify patterns, optimize future actions, and consolidate learnings into a persistent memory system, akin to a form of reinforcement learning and self-correction. The article draws parallels to similar features in other AI agent systems like Hermes Agent and OpenClaw, which also implement mechanisms for reviewing historical data, extracting reusable "skills," and strengthening long-term memory. It notes a key difference from human dreaming: these AI "dreams" still consume computational resources and user tokens. Further context is provided by discussing the technical challenges of managing AI "memory" or context, highlighting the computational expense of large context windows and innovations like Subquadratic's new model claiming drastically longer contexts. The core critique argues that this strategic use of human-centric vocabulary does more than market products; it subtly reshapes user perception. By framing algorithms with terms associated with consciousness, companies blur the line between tool and autonomous entity. This linguistic shift can influence user expectations, tolerance for errors, and even perceptions of responsibility when systems fail, potentially diverting scrutiny from the companies and engineers behind the technology. The article concludes by speculating that terms like "daydreaming" for predictive task simulation might be next, continuing this trend of embedding the idea of an "inner life" into computational processes.

marsbit05/11 00:15

Your Claude Will Dream Tonight, Don't Disturb It

marsbit05/11 00:15

DeepSeek V4 Finally Released, Breaking the Strongest Closed-Source Monopoly, Explicitly Partnering with Huawei Chips

DeepSeek AI has officially released DeepSeek-V4, available in two versions: the high-performance **DeepSeek-V4-Pro** (49B activated parameters, 1.6T total) and the more efficient **DeepSeek-V4-Flash** (13B activated parameters, 284B total). Both support a 1M context length, making long-context capability a baseline feature rather than a premium offering. The Pro version rivals top closed-source models in agent capabilities, world knowledge, and reasoning performance. It outperforms Claude Sonnet 4.5 in agentic coding and approaches Claude Opus 4.6 (non-thinking mode) in quality. The Flash version offers competitive performance at a lower cost, though it lags in highly complex tasks. A key technical innovation is a new attention mechanism that reduces computational and memory demands for long contexts. The models are optimized for agent frameworks like Claude Code and OpenClaw. API services are available with support for both OpenAI and Anthropic-style interfaces. DeepSeek also announced upcoming support for Huawei’s computing hardware in the second half of the year. The models are open-sourced on Hugging Face and ModelScope.

marsbit04/24 04:21

DeepSeek V4 Finally Released, Breaking the Strongest Closed-Source Monopoly, Explicitly Partnering with Huawei Chips

marsbit04/24 04:21

The Correct Way to Handle Claude Code Context: Avoid the Longer the Session, the 'Dumber' the Model

Anthropic has introduced a new /usage command for Claude Code, coinciding with its expanded 1 million token context window. This update addresses a key challenge: context rot, where model performance degrades as the context grows, due to attention dilution across excessive tokens. The article emphasizes strategic context management through five key actions: Continue, Rewind, Clear, Compact, and Subagents. It advises starting new sessions for new tasks but retaining relevant context for related work. The Rewind feature (double Esc or /rewind) is highlighted as a superior method for error correction, allowing users to revert and re-prompt from a specific point. Compaction (/compact) summarizes conversation history into a concise summary, though it can fail if the model misjudges future task relevance. In contrast, /clear requires manual summarization for a fresh start. Subagents are recommended for tasks generating disposable intermediate outputs, as they operate in isolated contexts and return only final results. The core recommendation is to proactively manage context—especially before model performance declines—to maintain high-quality outputs with Claude Code.

marsbit04/16 10:36

The Correct Way to Handle Claude Code Context: Avoid the Longer the Session, the 'Dumber' the Model

marsbit04/16 10:36

Thin Harness, Fat Skills: The True Source of 100x AI Productivity

The article "Thin Harness, Fat Skills: The True Source of 100x AI Productivity" argues that the key to massive productivity gains in AI is not more advanced models, but a superior system architecture. This framework, "fat skills + thin harness," decouples intelligence from execution. Core components are defined: 1. **Skill Files:** Reusable markdown documents that teach a model *how* to perform a process, acting like parameterized function calls. 2. **Harness:** A thin runtime layer that manages the model's execution loop, context, and security, staying minimal and fast. 3. **Resolver:** A context router that loads the correct documentation or skill at the right time, preventing context window pollution. 4. **Latent vs. Deterministic:** A strict separation between tasks requiring AI judgment (latent space) and those needing predictable, repeatable results (deterministic). 5. **Diarization:** The critical process where the model reads all materials on a topic and synthesizes a structured, one-page summary, capturing nuanced intelligence. The architecture prioritizes pushing intelligence into reusable skills and execution into deterministic tools, with a thin harness in between. This allows the system to learn and improve over time, as demonstrated by a YC system that matches startup founders. Skills like `/enrich-founder` and `/match` perform complex analysis and matching that pure embedding searches cannot. A learning loop allows skills to rewrite themselves based on feedback, creating a compound improvement effect without code changes. The conclusion is that 10x to 1000x efficiency gains come from this disciplined system design, not just smarter models. Skills represent permanent upgrades that automatically improve with each new model release.

marsbit04/13 04:19

Thin Harness, Fat Skills: The True Source of 100x AI Productivity

marsbit04/13 04:19

活动图片

Industry News

Project Updates