
Claude Code secrets leak: check your settings.local.json now
The Claude Code secrets leak explained: how 'don't ask again' saved passwords in settings.local.json, who is affected, and how to check and fix your repos.
Practical perspectives on building, connecting, and investing in the software behind your business.
A practical way to compare workflow fit, ownership, and long-term responsibility before choosing what to build or buy.

28 articles

The Claude Code secrets leak explained: how 'don't ask again' saved passwords in settings.local.json, who is affected, and how to check and fix your repos.

How to protect AI API keys after Black October: what LLMjacking is, why hosting platforms were hit, and the rotation and spend-limit steps to take this week.

AI shopping agents are part of Black Friday 2026. See what Google Universal Cart and ChatGPT shopping change, and the product data checks to make this week.

Anthropic IPO by the numbers: revenue, losses, customers, the $895 billion compute bill, and who controls the company, taken from its SEC filings.

Choose a synchronization approach around the age of information your workflow can tolerate and how staff handle delayed updates.

Use the same workflow, evidence requests, and delivery questions to compare software teams beyond their portfolios.

Find a bounded workflow with clear inputs, decisions, exceptions, and a measurable reason to automate it.

Decide who owns customer details, order status, and account changes before connecting sales and operations software.

What to agree before connecting your point of sale and online store, including available stock, returns, and failed updates.

Cut scope around a complete user outcome, distinguish a prototype from a live release, and make the deferred work explicit.

Separate a frustrating screen from a structural limitation, and compare improvement, extension, and replacement with evidence.
Bring us the problem. We’ll help you work out the next step.