Claude

Developer tasks, maintained context, and checked results with Claude.

Claude

Start here: Projects: what belongs in one, what poisons it

Admin controls: what you can actually govern Claude
The settings that exist, the defaults that differ between Team and Enterprise, and the gap where local sessions sit outside central control.
Using it as an accessibility tool, and its blind spots Claude
Genuinely useful as assistive technology, with one structural catch: the person relying on the output is often the one who cannot check it.
Artifacts: turning a conversation into something you can use Claude
A described idea becomes a working app in the side panel. The skill is the same as ever — iterate deliberately, and break it before you share it.
Connectors: what you hand over when you connect Drive Claude
A connector inherits your access, so its reach equals yours. That is the security model and the risk in one sentence.
Files, images and PDFs: what actually gets read Claude
A PDF over 100 pages has its text read and its charts ignored, silently. Knowing what is extracted from what saves you trusting an answer built on half a document.
Getting your data out Claude
Export lives in Settings, Privacy, arrives by email and expires in 24 hours. Conversations come out but cannot go into another personal account.
Memory across chats: what persists and what does not Claude
Memory is a separate store of topics that gets re-injected into new conversations. It is not the model recalling you, and it is editable.
Projects: what belongs in one, what poisons it Claude
Project knowledge is shared across every chat in the project. Past a size threshold it quietly stops being read whole and starts being searched.
The training toggle, retention, and what you agreed to Claude
Consumer and commercial plans have different rules. Most people do not know which one they are on, and the difference is measured in years.
Voice, mobile and desktop: same Claude, different affordances Claude
The model does not change between surfaces; what you can feed it and check does. Pick the surface by the task's input and its review needs.
Web search and citations: reading past the summary Claude
A citation proves a page was retrieved. It does not prove the page says what the sentence attached to it claims.
Which plan, honestly Claude
How to tell which tier you actually need, and the two situations where upgrading does not fix the thing you are upgrading to fix.
Chat, Projects, Cowork or Code: picking the right mode Claude + Cowork + Claude Code
Four surfaces, four cost profiles. Picking wrong is the most common reason people burn an allowance on work that did not need it.
What changed on this site Claude
Corrections, retractions and findings worth knowing about if you read something here before. Silent on typos and tidying.
Incident response when an agent did something Claude + Cowork + Claude Code
The playbook assumes a human actor and an agent breaks its first three questions. Decide before the incident what your records will be able to say.
Workflow: debugging a failure Claude + Claude Code + Anthropic API
Narrowing costs four times what diagnosing costs. Put the cheap model on the search and the expensive one on the thirty seconds that decide the answer.
Workflow: a refactor across several files Claude + Claude Code + Anthropic API
The plan is 1% of the tokens and decides the other 99%. Everything else is mechanical, and mechanical work does not need the expensive model.
Workflow: researching and synthesising Claude + Claude Code + Anthropic API
Reading thirty sources costs eight times what thinking about them costs. This is the workflow where model choice saves the most.
Workflow: reviewing a change Claude + Claude Code + Anthropic API
Three steps, three different models. Reading is not judging, and paying Opus rates to read a diff is the commonest waste in this workflow.

Check models, access, and limits