Claude

Started: 19/04/2026

A running, public notebook of friction points I run into while using Claude — Claude Code, the desktop/web apps, and the API. Small discoveries, workarounds, rough edges, and the occasional "why is it like this?" observation.

These are personal notes, not prescriptive guidance. Claude moves fast, so expect individual entries to become stale or obsolete over time. Where possible, each note is dated so the reader can judge whether it still applies.

How this repo is organised

• notes/ — one markdown file per friction point, each dated and self-contained.
• grounding/claude-docs/ — point-in-time snapshots of official Claude documentation used as a grounding reference.
• grounding/answers/ — answers to Claude-related questions grounded in the snapshots above.
• .claude/skills/refresh-claude-docs/ — skill to re-fetch the doc snapshots and flag stale answers.
• README.md — the index below, linking each note with a one-line summary.

Notes Index

Note	Date	Summary
Claude scaffolds skills/commands/agents at repo root instead of under .claude/	19/04/2026	Project-scoped components need .claude/skills/, .claude/commands/, .claude/agents/ — top-level folders are silently ignored.
Plugin user data has a standard path but no cross-device sync story	19/04/2026	${CLAUDE_PLUGIN_DATA}, pluginConfigs, and keychain credentials are all per-device; no documented export/import or sync contract.
The agentic-workspace model is local-centric, which blocks portability and always-on execution	19/04/2026	Miniaturised workspaces are great, but runtime is pinned to one device — no hosted execution, so autonomous/scheduled agents need the laptop to be awake.

Contributing / Feedback

This is a personal notebook shared as an open-source resource. If you recognise a friction point that's since been fixed, or have a better workaround, feel free to open an issue or PR.