Tag: claude-code
Is a consumer Claude plan safe for client data, and is it cheaper than Team?
Claude Max and Ultra run under the Consumer Terms, which carry no data processing addendum, so I keep client personal data on Team or Enterprise. On price, Max costs the same per five-hour session as a Team seat billed monthly. What Ultra buys is a higher ceiling for one heavy Claude Code user.
Claude inference hooks cannot see a screenshot
Anthropic now lets an Enterprise organisation put its own server in front of every prompt and return allow or deny before the model runs. It is the strongest inline control Claude has shipped. It also never receives raw image bytes, so a screenshot of the document you are trying to stop walks straight through, and the failure mode when your server goes down is a setting somebody has to choose.
The Claude Enterprise admin console has 25 sections and no map
Claude Enterprise puts 25 settings sections behind one nav, grouped into four blocks that do not match how anybody actually governs AI. Here is the whole tree, what each block controls, and the six settings worth opening on your first day as an Owner rather than the twenty-five you will otherwise scroll past.
macOS TCC broke brew, mise and Claude Code at the same time
Three tools failed within a minute of each other with three unrelated errors, and the folder they blamed had ordinary permissions the whole time. macOS TCC had revoked it. Two tccutil resets fixed that with no restart, because Terminal and Claude Code hold separate TCC identities and each one needs its own grant.
Claude for Excel cannot save a file, and the error will not tell you that
Ask the Claude add-in in Excel to roll a workbook forward into next month and you get a permissions error, which reads like a misconfiguration and is not one. The add-in has no file management at all, and that limit is missing from the unsupported list. Here is what it does do well, why it beat Claude Code on the same spreadsheet, and the settings field that fixes the complaint everybody has.
How to run many Claude Code sessions without duplicate work
Claude Code sessions can now message each other over a Unix socket on your own machine. I had 23 sessions running and only 14 of them could see each other. Here is what the message channel fixes, what it cannot fix, and why the guard I trusted for months was never a guard at all.
Two of your agents never read your CLAUDE.md
Claude Code loads your CLAUDE.md into every subagent except two. Explore and Plan skip it by design, and no setting changes that. So the agents you fan out most widely are the ones that never see your rules. ETH Zurich measured what the file costs on the occasions it does load.
A merge queue is theatre without a test oracle
Merge queues, merge trains, and speculative merging all rest on one assumption nobody states: that a per-branch green tick means the code works. Our own CI runs no unit tests at all, and master went red twice in two days from pull requests that were each green on their own. Here is what to build before you buy the queue.
What a git worktree does not isolate
A git worktree isolates your working directory and your index. It does not isolate the stash stack, which is shared by every checkout in the repository. Here is what I measured on git 2.50.1, why MERGE_AUTOSTASH escapes the problem through an accident of spelling, and how one defensive stash can make a worktree look safe to delete.
An MCP server is unreviewed code with your file system in scope
Treat every MCP server as untrusted code that runs with the access your agent has, because that is what it is. Anthropic docs say the directory lists connectors but does not security-audit them. A registry of approved servers with nothing enforcing it is a memo. The control that binds is a managed allowlist matched by URL or command, never by name.
Your Claude Code deny rules are not a security boundary
Before you hand Claude Code to hundreds of people you add deny rules for .env and credentials and feel locked down. You are not. Those rules govern Claude own tools, not a Python one-liner that opens the same file, and the control that actually holds, the OS sandbox, reads your whole machine by default and fails open when it cannot start. The baseline worth setting is real. Its dangerous gaps are the defaults you never changed.
Claude Code loop is for the work you watch
Claude Code /loop reruns a prompt on an interval inside your session. It is perfect for babysitting a deploy or a test run, and wrong for anything that has to keep going while you are away. It also exposes a durable flag that, on version 2.1.185, quietly writes nothing to disk. Here is how to use it well.
How to schedule Claude Code on your own machine
You want a Claude job to run every few hours on your Mac, not in the cloud. A cloud routine cannot do it, because it never touches your machine. Here are the local options that can, why launchd beats cron for this, and a working LaunchAgent that pulls every one of my repos on a schedule.
Can AI actually do accessibility testing? I ran it on my own product
Automated accessibility tools catch maybe a third of WCAG problems. I pointed Claude Code at Tallyfy, my own product, and let it run a real WCAG 2.2 audit with a live screen reader across four codebases. It found bugs that axe-core cannot see, and it showed clearly where the work still needs a person.
Claude Code behind a TLS-inspecting proxy: configure the tool, not the proxy
Locked-down shops reach for a proxy exception to make Claude Code connect. Wrong move, and it fails anyway. Claude Code does not pin certificates, so it works through full TLS inspection once you teach it to trust your corporate root CA. The fix is a couple of environment variables and an egress allowlist, not a hole in the proxy.
How to run a long autonomous Claude Code job without it drifting
The hard part of a big AI job is not the work. It is making the agent run for many sessions without drifting or claiming it is done when it is not. I used an accessibility audit across four codebases as the test. The setup that kept Claude Code on track was a git ledger, atomic parallel claims, and two verification passes.
How I run my whole consulting practice with Claude
I run Blue Sheen, the firm I lead with Pravina, through Claude and Claude Code. The practice lives in a version-controlled folder that Claude reads at the start of every session, with Close CRM as the source of truth. This is the real workflow stage by stage: prospecting, proposals, delivery, and the judgment a human still has to own.
When to use a dynamic workflow
A dynamic workflow in Claude Code runs up to sixteen subagents at once and a thousand across a job. That power is wasted on most tasks. This is the decision I use before reaching for one: when a single agent wins, when a dynamic workflow earns its cost, and when the answer is to not automate at all.
Dynamic workflows: parallel verification at scale
Dynamic workflows in Claude Code run tens to hundreds of subagents that check each other before anything reaches you. The parallelism is not the interesting part. The verification is. Here is how I am using one to re-verify around 300 posts on this site, and when it earns its cost.
Claude Code to Claude for Chrome: the handoff pattern
Claude Code lives in your terminal. Claude for Chrome lives in your browser. They do not share context. So your Code session writes a self-contained prompt your for-Chrome session can run, and the browser job gets done. Plus how the native paths work on macOS, Windows, and Edge today.
CLAUDE.md hierarchy: lock at two levels, split the libraries, audit the rest
CLAUDE.md hierarchy looks tidy in a personal repo. Push it across departments and it splits into a tree most users cannot reason about. Lock at two levels. Split read-only governance from read-write working content. Run a seven-check audit on every new file. Anything deeper is a vanity hierarchy that breaks in weeks.
A Claude desktop setup guide for corporate networks
Installing Claude on a personal machine takes a minute. On a corporate machine the install works and then nothing connects. This setup guide covers the clean install on macOS and Windows, then the network layer, proxy, TLS inspection, and the outbound allowlist, where the afternoon actually goes.
A complete guide to working with Claude
Working with Claude now means a dozen things: Claude Code, the Desktop app, agents, the partner network, certifications, connectors. This is the map. A hub that lays out the five regions of working with Claude and links each one to a deeper guide.
Claude Code effort mode and where it falls short
Claude Code effort mode looks like a cost dial: turn it down to spend fewer tokens. The official docs say otherwise. Effort is a behavioral signal, not a strict budget, so low effort does not reliably cut spend and can quietly raise it. Here are the five levels, where they stop, and how to set effort with intent.
Claude Code enterprise security is a design problem
Most guides to running Claude Code in an enterprise stop at the install. That is the easy ten percent. The real work is the security design around an agentic tool that runs commands and reads files: the audit trail, prompt injection, permission modes, and a managed policy file.
Claude Projects vs a git fileshare for teams
Claude Projects works well for one person. For a team, it is missing the thing collaboration is built on: version control. No diff, no history, no rollback. Here is the case for a git-backed fileshare driven by Claude Code instead, and the line where each one wins.
How Claude Code scheduled jobs actually work
Claude Code scheduled jobs come in three forms with very different guarantees: the in-session /loop, Desktop tasks, and Cloud routines. A missed run does not queue up a backlog. And despite a common belief, none of them creates a Windows Task Scheduler entry or a .bat file. Here is how each one actually behaves.
How Claude Code stop hooks work
A Claude Code stop hook runs the moment Claude finishes a turn and can refuse to let it stop. It is the one hook that inverts control: Claude must pass your check before the turn ends. This post covers what a stop hook is, why exit code 2 is the whole game, the infinite-loop trap to avoid, and the patterns worth wiring up.
How the general-purpose agent works in Claude Code
The general-purpose agent in Claude Code is not the main agent and not something you pick. It is a built-in subagent Claude routes to on its own for complex, multi-step work. It inherits your model and, by default, runs in its own fresh context that Claude briefs with a short summary. This post explains how it actually works and what that costs you.
How to budget tokens in Claude Code
A surprising Claude Code bill is almost never one big expense. It is four different cost shapes stacked up: a context window that bills every turn, subagents that each cost a fixed chunk, skills that cost almost nothing until used, and caching that can cut the recurring cost or not. Budgeting tokens means knowing the four shapes.