Credential discipline
On the difference between being careful with secrets and never having to be.
A secret that never enters the conversation can’t leak from it. The catch everywhere else is that keeping it out stays your job to remember. CRAFT for Claude Cowork is built so that it isn’t.
The moment you hand over a key
You’re wiring the assistant up to do something real — post on a schedule, pull from an API, touch a repository. It needs a credential. The quickest way forward is to paste the token into the chat, or drop it into a project file where the assistant can read it. It works. And now the secret sits in a transcript that gets logged, a file that syncs to the cloud, a screenshot, a copy that rides along into the next session. The careful move is to never do that — but careful is a thing you have to remember, every time, including late at night when you just want the thing to run.
Everyone says “be careful”
Reach for almost any tool and the credential advice is the same: keep secrets in environment variables, don’t commit them, don’t paste them into a prompt. It’s good advice. It also hands you the whole job of following it, forever. A feature list will say the tool “supports secure credentials” — nearly all of them do, and read side by side the checklists look identical, the way two cars both list headlights. And all of that advice is about files and repositories. None of it is about the new place a secret can end up once an assistant is in the loop: the conversation itself.
The difference is the shape, not the reminder
CRAFT’s version isn’t a sturdier reminder to be careful. It’s an arrangement where the careless path isn’t on the table. The credential lives in a dedicated folder that’s ignored by design, and it’s handed to whatever needs it out-of-band — passed across directly at the moment it’s used, never written into the conversation. So it isn’t in the chat history, and it isn’t in the project files that sync off your machine. The most ordinary way a secret gets loose — sitting in plaintext somewhere a process can read it and carry it onward — is designed out of the workflow instead of guarded against.
Two paths a credential can take: pasted into the conversation, or kept out of it by design.
That’s a smaller promise than it sounds, and that’s the point: it removes one common way things go wrong, so getting this right stops depending on you remembering to.
A project folder — structure real, details invented
my-project/
CRAFT Project Files/ ← your work — syncs and travels with you
.credentials/ ← ignored by design — never leaves your machine
service.token (handed over out-of-band, never typed in chat)
The folder names are illustrative; the arrangement — a dedicated ignored folder, passed out-of-band — is the real one.
Why it’s built this way
This reflex has a source. CRAFT is built by one person who brings a safety-first mindset from a day job in cybersecurity. In that line of work you learn a particular move: when something keeps going wrong because a human has to remember a step, you don’t write a louder reminder — you remove the step. A credential that never enters the conversation is that move, written into a framework. Provenance, here, is accountability: the discipline is a deliberate choice by someone who does this kind of work for a living — not a promise that nothing can ever go wrong.
You don’t write a louder reminder — you remove the step.
The rest of the discipline
The same habit shows up in a few other places: releases are signed and list their checksums, so you can confirm a download is exactly what was published; and the framework’s own files stay in a read-only folder, kept separate from your work so the two never mix. None of this is a wall around your data. All of it is the same idea — make the trustworthy path the easy one.
Wire it into something real
CRAFT for Claude Cowork is free during beta and lives on GitHub — no login, no email, no paywall. Wire it into something that needs a key, and the credential discipline is the part you notice by its absence: nothing to paste, nothing to remember to delete later.
Handing an assistant a key shouldn’t mean leaving copies scattered across your files. Downloading CRAFT is free during beta — the credential discipline comes with it, not as a setting you have to find.
Free during beta. The download is ungated — no account, no email, no checkout. CRAFT for Claude Cowork runs on Claude Cowork, so you’ll need Cowork available in your Claude plan; CRAFT adds no cost, account, or gate on top of it. More on what it is
CRAFT for Claude Cowork is an early framework, in beta, and AI can make mistakes — review anything that matters before you rely on it. Keeping a credential out of the conversation removes a common way secrets get loose; it doesn’t make risk zero, and nothing here should be read as a promise that it does.
