--- title: "Claude Code /init: Check what your file leaves out." description: "Audit the CLAUDE.md that /init wrote. Check stale paths and commands, then map missing answers to maintenance, routing, search, or archives." canonical: "https://scalewithsearch.com/articles/claude-code-init-limitations" date: "2026-03-23" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Find where Claude Code /init stops and plan the memory it leaves out. You ran `/init`. Claude Code scanned your repository and wrote a `CLAUDE.md` with your language, framework, test conventions, and some notes on the folder layout. It was a good start. A week later, Claude Code still asked about things the file should cover. You added rules. The file grew to 200 lines, then 400. Each new session still started cold. Claude Code knew your linter settings. It did not know your business. This is not a defect in `/init`. It does what it claims. The problem is what people assume the file replaces. This article maps what `/init` produces, six things it does not do, and the cases where its output is enough. ## What /init produces Run `/init` in a project folder, and Claude Code writes a `CLAUDE.md`. The contents vary by project. The shape stays the same: ``` # Project Name ## Build & Test - `npm run build` to compile - `npm test` to run all tests - `npm run lint` for style checks ## Code Style - TypeScript with strict mode - Prefer const over let - Use async/await, not callbacks ## Project Structure - src/ contains source files - tests/ contains test files - Config in root directory ``` Real output may carry more detail about your framework or deploy process. It is always a set of static observations about the current codebase, written as rules and conventions. The scan takes about 30 seconds. The file is useful. A new developer benefits from it. Claude Code benefits too: it will not suggest callbacks in an async/await codebase. The confusion starts when someone treats the file as a memory system. For the split between standing rules and business facts, read [context file versus CLAUDE.md](/articles/context-file-vs-claude-md-business-project). ## Six things /init does not do ### It does not update the file `CLAUDE.md` is a snapshot. You move from Express to Fastify. You migrate from Jest to Vitest. You adopt a monorepo. The file still describes last month's architecture. Nothing watches for drift between the codebase and the file. You maintain the file by hand, or it decays. A memory system adds scheduled maintenance: a job checks the context files against the source of truth and flags or corrects stale facts. ### It does not route context by domain Suppose you work across several domains. You run a sales pipeline in a day job, run a consulting practice, and keep a personal knowledge vault. Each domain has its own vocabulary, contacts, and rules. "Leads" at 2 p.m. means something different from "leads" at 9 p.m. `/init` writes one file for one project. It has no routing table, no keyword map, and no conditional load. A memory system keeps one `_context.md` file per domain and a routing table that loads the right one from the words in your prompt. "Pipeline" loads the sales context. "Retainer" loads the consulting context. You do not have to name the domain each time. ### It does not set up search across your knowledge base Your `CLAUDE.md` may point to other files, such as `docs/architecture.md`. Claude Code can run keyword and file-name searches in the project folder. That works when you know the words. It fails when a note uses different words, or when the answer sits in a conversation from last month. `/init` adds no index. It adds no semantic search that finds notes by meaning. It adds no archive of past sessions. With 2,000 notes in 50 folders, a note about a client's billing preference stays hard to find unless you supply the path. A memory system layers several search methods. Pattern search finds exact matches. Vector search finds concepts. A structure-aware search follows the vault's layout. A full-text index covers every past session. ### It does not create hooks or skills Claude Code supports hooks, but `/init` does not write any. Without them, a session reads `CLAUDE.md` and waits. No step loads today's calendar at session start. No step archives the transcript at session end. No trigger sends a Telegram alert when a CRM record changes. A memory system adds hooks that inject current state and archive each session into a searchable ledger. It adds skills: slash commands that run multi-step operations. It adds event triggers that act on a schedule or an outside signal. ### It does not provide an always-on server Close your laptop, and Claude Code stops. `/init` is a local operation for a local tool. It assumes you sit at the terminal. Business events do not wait for you. A lead fills out a form at 3 a.m. A competitor publishes on Saturday morning. A teammate mentions you in Slack while you drive. A memory system can include a VPS that runs scheduled jobs, watches outside systems, and sends alerts to your phone while the laptop is closed. ### It does not create safety gates Give Claude Code write access to your CRM API, and it will write to your CRM. `/init` creates no guardrails around destructive operations. It adds no dry-run mode and no confirmation step for bulk actions. It does not separate "read this record" from "change the record for a large deal." `/init` describes a codebase. It does not govern operations. A memory system adds explicit limits. Write-blocked areas need manual approval. Batch thresholds pause for confirmation. An audit trail records each autonomous action. The [approval article](/articles/who-approves-what-an-ai-agent-sends) shows how to assign those decisions. A prose rule in `CLAUDE.md` is context, not enforcement, so put the real denial in permissions or tool design. ## Compare /init with a full memory system Count the components that a persistent memory system uses: | Component | Covered by /init? | Full memory system | |---|---|---| | Context file | Partly | Several domains, maintained on a schedule | | Domain routing | No | Keywords trigger the context load | | Vault architecture | No | A structured knowledge base with conventions | | Pattern search | No | Pattern matches across all files | | Semantic search | No | Vector embeddings for concept queries | | Session archive | No | Each conversation stored, indexed, and searchable | | Session hooks | No | Context injected at start; archive written at end | | Skills | No | Reusable multi-step slash commands | | Safety gates | No | Write blocks, dry runs, confirmation thresholds | | Correction record | No | Corrections propagate and do not revert | | Voice and style rules | No | Calibration for tone, structure, and density | | Scheduled maintenance | No | Context checked against current reality | | Always-on server | No | A VPS for background operations | | Notifications | No | Alerts through Telegram, Slack, or another channel | `/init` covers one of the fourteen rows, and only in part. Its file covers one domain, the codebase, without the surrounding parts that keep it useful over months. Not every business needs all fourteen. The table shows what you give up when the file is the whole setup. ## Watch how a static file decays A static file decays on a predictable path. This example shows the pattern over ten weeks. In week 1, everything works. Claude Code reads the file, follows the conventions, and produces good output. By week 3, you have refactored two modules. The file still describes the old structure, and Claude Code suggests patterns you retired. You spend 20 minutes on an update, once. By week 6, about a third of the file is out of date. You stopped updates because the effort felt larger than the return. Output quality varies, so you write longer prompts. Each session starts with three paragraphs of setup. By week 10, you are back where you started. The file exists, but its instructions have drifted so far that following them gives worse output than ignoring them. You paste context by hand again. This is not a failure of discipline. Manual upkeep of a static file against a changing system grows with the system's complexity. Few people keep it up. The fix is to automate the upkeep and to record each correction where the next session reads it. The [corrections article](/articles/corrections-become-system-memory) shows how one fix becomes a standing rule. ## Worked example: audit the file /init wrote Run this check on your own `CLAUDE.md` before you decide what to add. 1. Open the file and mark each line as a build command, a style rule, a structure note, or a business fact. 2. For each structure note, confirm that the path still exists. 3. For each build command, run it and confirm that it still works. 4. List three questions you asked Claude Code this month that the file did not answer. 5. For each question, write where the answer lives: a file, a person, a past chat, or nowhere. 6. Mark each answer location as searchable by keyword, searchable by meaning, or not searchable. Read the result by row. Stale paths or broken commands mean you need scheduled maintenance first. Answers that live in past chats mean you need a session archive. Answers that live in another domain's files mean you need routing. Questions about data that changes overnight mean you need hooks or an always-on server. A question about a write to a live system means you need a safety gate before anything else. Keep the business facts out of `CLAUDE.md` as you add them. The file should stay a set of work rules that points to the facts. The [minimum-context guide](/articles/what-context-should-an-agent-read) shows how to load the right fact files only when a job needs them. ## Know when /init is enough Three cases do not need more than the file. The first is short work by one developer on one project, such as a weekend build. The codebase fits in your head, and a basic `CLAUDE.md` is enough. The second is code-only use. You use Claude Code only for code, with no business context, no multi-domain work, and no CRM connections. A style guide is all you need. The third is a trial period. You are still testing whether Claude Code fits your workflow. Run `/init`, use the file, and notice where it falls short. Then decide whether those gaps matter. If you manage clients, work across several business domains, or need context that lasts longer than one coding session, treat `/init` as the starting line. In a full system, the context file is not 30 lines of build commands. It records how the AI works with you: your voice rules, your correction history, your domain vocabulary, and your hard limits. ## Related: AI memory - [Copy a CLAUDE.md template for your role and adapt it in 30 minutes](/articles/claude-md-template-examples) - [Turn each business document into a data feed your AI memory can trust](/articles/documents-as-data-feeds-ai-memory) - [Route prompts to the right context file with a keyword table](/articles/ai-context-routing-explained) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```