Teach your agent a folder of personal scripts

Claude Cowork learned a set of homegrown automations from a scripts folder and kept using them in its own app.

Done with Claude Cowork· Intermediate· Jan 2026

What they did
Tomasz Tunguz gave Claude Cowork access to a local directory containing dozens of scripts he had written over roughly a year. The collection handled work such as email triage, CRM changes, startup research, and response drafting. Cowork read through the files, broke down the logic, and stored it over eleven steps so the routines could be used inside the Cowork app rather than only in the terminal.
How it went
The same functions were available in the new interface with no drop in capability. The first version was sluggish at launch, failed twice during startup, and also altered access permissions in the original Claude Code installation.
Tips
Have the agent summarize the folder before it starts acting on anything. If a workflow could touch permissions, external accounts, or outgoing actions, make it stop and ask before continuing.

Try it yourself with Claude Cowork

My scripts live in [folder path]. Inspect the folder and explain each script in plain language, including any email, CRM, research, or drafting tasks it supports. Save the useful procedures in memory so you can reuse them later, but do not run, edit, move, or share anything yet. When you finish, show me a list of the capabilities you found and how each one is triggered, then wait for my approval before you change permissions, send messages, delete files, or submit anything.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on x.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.