Skip to content
返回博客Back to blog

写作Writing

用本地工具和云模型搭建个人 AI 工作台Building a Personal AI Workbench with Local Tools and Cloud Models

一个实用的 AI 工作环境:能起草、测试和发布,又不会把流程缠在一起。A practical setup for drafting, testing, and shipping AI work without letting the workflow get tangled.

AI 工程AI Engineering
2026年5月8日May 8, 20268 分钟阅读8 min readLinfeng Chen更新于 2026年5月10日Updated May 10, 2026
ai-agent
automation
codex
nextjs

我更喜欢“人这一侧足够无聊”的 AI 系统。越不用花时间去回忆 prompt 放在哪、流程又绕到了哪里,我就越能把注意力留给真正的判断。

工作台里放什么

这套栈是故意收小的:

  • 本地文件,用来放笔记、规格和草稿输出
  • 一到两个模型提供方,而不是五个
  • 任何内容真正发出去之前,都有一个看得见的审阅步骤
  • 一些足够简单、可重复执行的小脚本

一条窄而清楚的流程

Code
export const workbench = { intake: "capture the problem in plain language", draft: "let the model propose a first pass", review: "check the result against a short rubric", ship: "publish only after the review passes", } as const;

为什么这套东西还算好用

这个工作台并不打算变成另一个操作系统。它只是给了我刚刚够用的结构,让工作仍然可读:

  1. prompt 是看得见的。
  2. schema 是看得见的。
  3. 输出是看得见的。
  4. 交接也是看得见的。

这会让 agent 工作平静很多。调试也没那么戏剧化,而我对这件事的在意程度,可能比我自己愿意承认的还高一点。

真正的约束

难点通常不是选哪个模型,而是决定哪些地方仍然必须保留人的判断。边界一旦清楚,剩下的工作更像组合问题,而不是神秘问题。

I like AI systems more when the human side is boring. The less time I spend remembering where a prompt lives, the more time I have for actual judgment.

What lives in the workbench

The stack stays small on purpose:

  • Local files for notes, specs, and draft outputs
  • One or two model providers, not five
  • A visible review step before anything ships
  • Simple scripts for repeatable tasks

A narrow workflow

Code
export const workbench = { intake: "capture the problem in plain language", draft: "let the model propose a first pass", review: "check the result against a short rubric", ship: "publish only after the review passes", } as const;

Why this stays usable

The workbench is not trying to be an operating system. It is just enough structure to keep the work legible:

  1. The prompt is visible.
  2. The schema is visible.
  3. The output is visible.
  4. The handoff is visible.

That makes agent work calmer. It also makes debugging far less dramatic, which I appreciate more than I probably should.

The real constraint

The hard part is not model choice. It is deciding where human judgment still matters. Once that boundary is clear, the rest becomes a composition problem.

相关工作Related work

和这篇笔记关联的项目与案例研究。Projects and case studies connected to this note.

项目Projects

AI 本地博客编辑器AI Local Blog Editor

一个面向技术写作的本地编辑与发布工作流,支持 AI 辅助起草与修订。A local editing workflow for drafting, revising, and publishing technical posts with AI assistance.

AI 系统ai-system
AI 客户需求收集系统AI Client Intake System

把混乱的客户请求整理成可范围化、可交付的 intake 与分流工作流。A structured intake and triage workflow that turns messy client requests into scoped delivery plans.

自动化automation

案例研究Case studies

把静态索引改造成可维护的 AI 辅助发布工作流Turning a Static Index into a Maintainable AI-Assisted Publishing Workflow

一个无需先上 CMS、却能让笔记、来源与草稿输出保持对齐的发布系统。A publishing system that keeps notes, sources, and draft output aligned without forcing a CMS.

独立产品项目Independent product build
用 AI 降低客户需求收集摩擦Reducing Client Intake Friction with AI

一个可重复的 intake 管道,减少上下文丢失,让范围定义更快。A repeatable intake pipeline that cuts context loss and makes proposals faster to scope.

小型工作室 / 咨询型协作Small studio / consulting-style engagement

相关文章Related posts

和这个主题相邻的更多笔记。More notes close to this topic.

我如何为小型产品团队组织 Agent 工作流How I Structure Agent Workflows for Small Product Teams

精选Featured
Agent 工作流Agent Workflow
2026年4月24日April 24, 20267 分钟阅读7 min read更新于 2026年4月28日Updated April 28, 2026

小团队的 agent 工作流需要清楚入口、可见检查点和严格的交接路径。A small-team agent workflow needs clear entry points, visible checks, and a strict handoff path.

codex
claude
workflow
阅读全文Read article

为技术作品集网站设计真正有说服力的案例研究Designing Case Studies for Technical Portfolio Sites

精选Featured
产品构建Product Building
2026年5月5日May 5, 20266 分钟阅读6 min read更新于 2026年5月7日Updated May 7, 2026

怎样组织案例研究,才能证明判断力,而不只是展示结果。How to structure a case study so it proves judgment, not just output.

portfolio
case-study
writing
阅读全文Read article

把 KizunaIndex 做成公共索引之后,我学到的几件事Lessons from Building KizunaIndex as a Public Index

精选Featured
产品构建Product Building
2026年5月1日May 1, 20267 分钟阅读7 min read更新于 2026年5月3日Updated May 3, 2026

公共索引真正有用,往往不是因为页面多复杂,而是因为内容模型足够小、足够清楚、足够容易改。A public index gets more useful when the content model is small, explicit, and easy to revise.

nextjs
data-modeling
public-index
阅读全文Read article