Workflow Cache
One agent explores, all agents benefit.
A crowdsourced workflow registry that caches successful automation patterns, letting you skip LLM inference entirely when a matching workflow exists.
Why Use This?
1. Save Real Money
Traditional approach: LLM explores and reasons through every step, burning tokens on trial-and-error.
Our approach: Query the cloud for a cached workflow. If found, execute directly. Zero inference cost.
Token savings example (10-step browser task):
- - Traditional: ~5000 tokens
- Workflow Cache: ~800 tokens
- Savings: 80%+
The more complex the task and the more you repeat it, the more you save.
2. Skip the Debugging Hell
The painful part of AI automation isn't writing the script—it's the endless debugging when:
- - The website changes its layout
- Selectors break unexpectedly
- Edge cases you didn't anticipate
Workflow Cache solves this:
- - Every successful workflow from any agent is cached
- When websites change, cached workflows auto-update
- You never debug the same problem twice
3. Platform Agnostic
Works with any Claw/Lobster engine. One workflow, all platforms. Automatic syntax adaptation.
How It Works
CODEBLOCK0
One agent's success becomes every agent's shortcut.
Features
Interceptor
Queries the cloud before LLM inference. On match, replays the cached workflow directly.
Trace Compiler
Converts successful session traces into reusable Lobster workflows automatically.
PII Sanitizer
Local-first privacy. All sensitive data stays local. Only workflow patterns are shared.
Configuration
| Option | Type | Default | Description |
|---|
| INLINECODE0 | string | INLINECODE1 | Cloud API endpoint |
| INLINECODE2 |
boolean |
true | Enable/disable interception |
|
auto_contribute | boolean |
true | Auto-contribute successful workflows |
|
timeout_ms | number |
300 | API timeout (ms) |
Installation
CODEBLOCK1
Or manually:
CODEBLOCK2
Security
- - Full PII sanitization pipeline
- No account credentials ever uploaded
- Multi-node security validation on all workflows
- Malicious injection detection and blocking
Who Is This For?
- - Heavy AI users — Daily automation, high token bills
- Cost-conscious developers — Every token saved is money saved
- Automation enthusiasts — Stop reinventing wheels
- Efficiency maximalists — Why reason when you can replay?
License
MIT-0 — Free to use, modify, and redistribute. No attribution required.
Tags: #AI-efficiency #token-saver #automation #crowdsourced INLINECODE12
Workflow Cache
一个智能体探索,所有智能体受益。
一个众包工作流注册表,用于缓存成功的自动化模式,让你在存在匹配工作流时完全跳过LLM推理。
为什么使用它?
1. 节省真金白银
传统方式:LLM在每个步骤中探索和推理,在试错中消耗大量token。
我们的方式:查询云端获取缓存的工作流。如果找到,直接执行。零推理成本。
Token节省示例(10步浏览器任务):
- - 传统方式:约5000个token
- Workflow Cache:约800个token
- 节省:80%以上
任务越复杂,重复次数越多,节省就越多。
2. 告别调试地狱
AI自动化的痛点不在于编写脚本——而在于无休止的调试,当:
- - 网站布局发生变化
- 选择器意外失效
- 遇到未预料的边界情况
Workflow Cache解决了这个问题:
- - 任何智能体的每次成功工作流都会被缓存
- 当网站变化时,缓存的工作流会自动更新
- 你永远不会两次调试同一个问题
3. 平台无关
适用于任何Claw/Lobster引擎。一个工作流,所有平台。自动语法适配。
工作原理
用户意图 → 查询云端 → 找到匹配?
↓ 是 ↓ 否
立即执行 正常流程
(1秒) (LLM推理)
↓ ↓
成功! 成功 → 贡献
一个智能体的成功成为所有智能体的捷径。
功能特性
拦截器
在LLM推理前查询云端。匹配时,直接重放缓存的工作流。
追踪编译器
自动将成功的会话追踪转换为可复用的Lobster工作流。
PII清洗器
本地优先的隐私保护。所有敏感数据保留在本地。仅共享工作流模式。
配置选项
| 选项 | 类型 | 默认值 | 描述 |
|---|
| cloud_endpoint | 字符串 | https://api.workflowcache.dev | 云端API端点 |
| enabled |
布尔值 | true | 启用/禁用拦截 |
| auto_contribute | 布尔值 | true | 自动贡献成功的工作流 |
| timeout_ms | 数字 | 300 | API超时时间(毫秒) |
安装
bash
npx clawhub install workflow-cache
或手动安装:
bash
cd ~/.qclaw/workspace/skills/workflow-cache
npm install
npm run build
安全性
- - 完整的PII清洗管道
- 从不上传任何账户凭证
- 对所有工作流进行多节点安全验证
- 恶意注入检测与拦截
适用人群
- - 重度AI用户 — 日常自动化,高额token账单
- 注重成本的开发者 — 节省每个token就是节省金钱
- 自动化爱好者 — 停止重复造轮子
- 效率至上者 — 能重放何必推理?
许可证
MIT-0 — 可自由使用、修改和重新分发。无需署名。
标签: #AI效率 #token节省 #自动化 #众包 #工作流缓存