WorkBuddy Is a Workbench, Not Another Chat Box
Assign a real job that can finish on your machine. Run one loop before skills and connectors. Short Q&A and cloud teammates belong elsewhere.
WorkBuddy's community guides describe a work system, not a rewrite of the official manual: get it running, finish one real job, then pack the method as a skill. Connectors and automation come after.workbuddy-guide workbuddy-yellow We keep that order. We do not keep the click path.
After reading, you should be able to answer:
- What kind of work belongs on WorkBuddy?
- Why is “install every skill, then work” backwards?
- How does it split from Doubao Work, Codex, and Grok Bot?
Fits: a completion you can accept on this machine
Sorting a local folder, walking a fixed path through a local app, turning one success into the same rule next time. The artifact is on your desk. Acceptance is a result you can see on the spot. The first job is still low-risk and reversible. See pick the first job.
Does not fit
- Short Q&A. A workbench is not for explanations.
- Pure repo coding. Tests, diffs, project instructions. See Codex.
- Work that must keep going on other people's sites after you close the lid. See Grok Bot. Office documents and tables in company space: Doubao Work.
Finish, then pack capability
Skills, connectors, and automation are containers for a method, not starting conditions. Without one accepted real job, packed capability has no comparison, and permission opens before the method exists. The blue book's path is: get it running, practice on cases, then fold the case into a system. The order is the judgment.workbuddy-guide