4.4 放下半年，拿起来继续

AI 协作中最让人头疼的场景之一：你做了一个项目，放了半年，回来继续做，发现 AI 什么都不记得了。

你打开一个新的对话，说"我们继续做之前的项目"——AI 一脸茫然。你开始复述项目背景、技术选型、之前做了什么、接下来要做什么。复述了半小时，AI 终于进入了状态。

AI Context Workspace 就是为了解决这个问题而设计的。

半年后，你回来，打开工作区，AI 读取：

  1. AGENTS.md——工作区结构，每个目录是干什么的
  2. background/——项目背景，技术选型，领域知识
  3. conventions/——工作规范，代码风格，质量标准
  4. artifacts/index.json——当前活跃任务列表
  5. 每个活跃任务的 artifact.json——做到哪了，什么状态
  6. 已归档的 archive/summary.md——之前完成了什么，关键决策是什么

整个过程不需要你说一句话。AI 读完这些文件，就恢复了所有的上下文，可以无缝继续工作。

这就是"上下文可持久化"的价值。

你不需要记忆，AI 不需要重训。工作区里的文件就是持久化的上下文。任务暂停了，状态写在 artifact.json 里。任务完成了，摘要写在 summary.md 里。背景变化了，更新在 background/ 里。

交接也是一样。

如果你需要把项目交接给另一个人（或另一个 AI），直接把工作区给他。他打开工作区，读一遍文件，就获得了你当时的所有上下文。不需要开会，不需要写交接文档，不需要口头解释。

这种"交接"甚至不需要人在场。 你可以把工作区放在 Git 仓库里，新的 AI 客户端克隆下来，就能开始工作。这就是 AI 时代的"交接"——不是把人叫来开会，是把上下文交给文件系统。

上下文管理最好的状态是：你觉得它不存在。

当你习惯了工作区的工作方式，你不会觉得"我在管理上下文"，你只是"在做项目"。上下文的管理是自动的、无感的。你写文件，AI 读文件，上下文自然流动。

这就是为什么 AI Context Workspace 最终可以让你放下半年，拿起来继续。因为上下文不在你的脑子里，也不在 AI 的对话历史里，它在文件里。

Comments

Post a Comment

Popular posts from this blog

How to turn off Sass warning prompts in Nuxt.js projects

Background of the Issue When developing projects with Nuxt.js, it’s common to encounter a large number of Sass-related warning messages in the console. These warnings mainly include: Warnings about the order of mixin declarations. Warnings about the use of Legacy JS API. Although these warnings do not affect the operation of the program, they can degrade the development experience by cluttering the console. Today, we will explore how to elegantly address this issue. Solutions 1. Disable Warnings via Configuration In the nuxt.config.js file, we can modify the Sass configuration to suppress these warning messages: export default { build: { loaders: { scss: { sassOptions: { quietDeps: true , // Suppress warnings from dependencies logger: { warn: function ( message ) { return null ; // Silence warning messages }, debug: function ( message ) { return null ; // Silence ...
Read more

Configuring SSH Access to a Docker Container via an Alternative Port

Configuring SSH Access to a Docker Container via an Alternative Port If you want to configure SSH access to a Docker container using an alternative port, such as port 6666 , follow the steps below carefully. This guide assumes that you have administrative access to your Docker host and are familiar with basic Linux commands. Step 1: Run the Container with SSH Service Start by running a new container from your image with port 6666 on the host mapped to port 22 inside the container: sudo docker run -it -p 6666 : 22 --name ssh-container testimage Make sure to replace testimage with the actual name of your Docker image. The --name option gives the container a specific name for easier management. Step 2: Install OpenSSH Server in the Container Once inside the container, update the package list and install the OpenSSH server: apt-get update && apt-get install -y openssh-server Step 3: Set the Root Password Set a password for the root user, which will be required when l...
Read more

Quickly Set Up a Cloud Database Using MongoDB Atlas

Quickly Set Up a Cloud Database Using MongoDB Atlas MongoDB Atlas is the official fully managed cloud database service from MongoDB, simplifying the deployment, management, and scaling of MongoDB in the cloud. This article will guide you on how to quickly create a MongoDB Atlas cluster and set up basic connection configurations. Creating a MongoDB Atlas Cluster Sign Up & Log In If you do not have a MongoDB Atlas account yet, head over to MongoDB Atlas to sign up. After logging in, click on “Build a Cluster” to start creating a new cluster. Select Cluster Configuration To meet the needs of most development and testing scenarios, you can choose the free tier (M0) shared cluster, which is usually sufficient for small applications or personal projects. When choosing a cloud provider, select based on your preference. Here we chose Azure, but AWS and GCP are also great choices. Specify Geographic Location For geographic location selection, choose according to your u...
Read more