{"id":5503,"date":"2026-04-09T13:57:30","date_gmt":"2026-04-09T13:57:30","guid":{"rendered":"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/"},"modified":"2026-04-09T13:57:30","modified_gmt":"2026-04-09T13:57:30","slug":"decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows","status":"publish","type":"post","link":"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/","title":{"rendered":"Decoding the .claude Folder: The Essential Guide to AI State Management in Modern Development Workflows"},"content":{"rendered":"<p>As the integration of Large Language Models (LLMs) moves from browser-based interfaces into local development environments, developers are increasingly encountering a new artifact in their project directories: the <code>.claude<\/code> folder. This hidden directory, typically generated by command-line interface (CLI) tools, agent frameworks, or integrated development environment (IDE) extensions powered by Anthropic\u2019s Claude models, represents a significant shift in how artificial intelligence interacts with local codebases. Far from being a mere temporary cache, the <code>.claude<\/code> folder serves as the operational nerve center for agentic workflows, acting as a bridge between the stateless nature of cloud-based LLMs and the stateful requirements of complex software engineering tasks.<\/p>\n<p>The emergence of this folder coincides with the rapid adoption of &quot;Agentic AI&quot;\u2014systems capable of planning, executing, and refining multi-step tasks autonomously. For these agents to function effectively within a local project, they require a persistent memory of previous actions, configuration settings, and context that the API itself does not inherently store. Understanding the architecture, purpose, and management of the <code>.claude<\/code> folder is now a requisite skill for developers looking to optimize their use of AI-driven development tools while maintaining project hygiene and security.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#The_Technical_Rationale_for_Local_State_Persistence\" >The Technical Rationale for Local State Persistence<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Anatomy_of_the_claude_Directory_A_Technical_Breakdown\" >Anatomy of the .claude Directory: A Technical Breakdown<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Configuration_and_Environment_Settings\" >Configuration and Environment Settings<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Context_and_Working_Memory\" >Context and Working Memory<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Agent_Definitions_and_Task_Workflows\" >Agent Definitions and Task Workflows<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Execution_Logs_and_Telemetry\" >Execution Logs and Telemetry<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Performance_Optimization_through_Caching\" >Performance Optimization through Caching<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#The_Operational_Lifecycle_How_the_Folder_Functions\" >The Operational Lifecycle: How the Folder Functions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Data_Efficiency_and_Cost_Implications\" >Data Efficiency and Cost Implications<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Security_Protocols_and_Management_Best_Practices\" >Security Protocols and Management Best Practices<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#The_gitignore_Mandate\" >The .gitignore Mandate<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Data_Privacy_and_Log_Management\" >Data Privacy and Log Management<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Resetting_the_AI_State\" >Resetting the AI State<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Broader_Impact_on_the_Software_Development_Life_Cycle_SDLC\" >Broader Impact on the Software Development Life Cycle (SDLC)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"http:\/\/drcrypton.com\/index.php\/2026\/04\/09\/decoding-the-claude-folder-the-essential-guide-to-ai-state-management-in-modern-development-workflows\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"The_Technical_Rationale_for_Local_State_Persistence\"><\/span>The Technical Rationale for Local State Persistence<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>At the heart of the <code>.claude<\/code> folder\u2019s existence is the fundamental limitation of Large Language Models: statelessness. Every time a request is sent to an LLM like Claude 3.5 Sonnet, the model processes that request in isolation unless a history of the conversation is explicitly provided. In a web chat interface, the platform manages this history on its servers. However, when using Claude as a local development tool\u2014where it might be tasked with refactoring a specific module, debugging a test suite, or generating documentation\u2014the model needs a localized &quot;working memory&quot; to ensure consistency across multiple execution runs.<\/p>\n<p>The <code>.claude<\/code> folder functions similarly to the <code>.git<\/code> directory for version control or the <code>.vscode<\/code> folder for editor settings. It provides a standardized location for tools to store metadata that does not belong in the source code itself but is essential for the tool&#8217;s operation. By localizing this data, developers can ensure that the AI &quot;remembers&quot; the specific constraints of a project, the progress of a multi-hour coding task, and the specific preferences defined by the user.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Anatomy_of_the_claude_Directory_A_Technical_Breakdown\"><\/span>Anatomy of the .claude Directory: A Technical Breakdown<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>While the exact contents of a <code>.claude<\/code> folder can vary depending on the specific tool or framework in use, most implementations follow a structured pattern designed for rapid read\/write access. The folder is prefixed with a dot, a standard Unix-like convention for hiding configuration files from the default directory view, emphasizing its role as a background system resource.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Configuration_and_Environment_Settings\"><\/span>Configuration and Environment Settings<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The <code>config.json<\/code> file is perhaps the most critical component. This file defines the operational parameters for the Claude integration within that specific project. It may contain instructions on which model version to use (e.g., Claude 3 Opus vs. Claude 3.5 Sonnet), token limits for individual sessions, and &quot;system prompts&quot; that define the AI\u2019s persona and rules of engagement. By storing these locally, the tool ensures that every developer working on the project\u2014or every subsequent run by the same developer\u2014adheres to the same logical framework.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Context_and_Working_Memory\"><\/span>Context and Working Memory<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The <code>memory\/<\/code> or <code>context\/<\/code> subdirectories act as the long-term storage for the agent. In these folders, the system stores snippets of relevant code, summaries of previous interactions, and documentation that the model has &quot;read&quot; and might need to reference again. This is particularly important for managing &quot;context window&quot; efficiency. Rather than sending the entire codebase to the API with every query\u2014which would be prohibitively expensive and slow\u2014the system uses the local memory folder to perform RAG (Retrieval-Augmented Generation), sending only the most relevant pieces of information.<\/p>\n<figure class=\"article-inline-figure\"><img src=\"https:\/\/www.kdnuggets.com\/wp-content\/uploads\/KDN-Shittu-Breaking-Down-the-.claude-Folder.png\" alt=\"Breaking Down the .claude Folder\" class=\"article-inline-img\" loading=\"lazy\" decoding=\"async\" \/><\/figure>\n<h3><span class=\"ez-toc-section\" id=\"Agent_Definitions_and_Task_Workflows\"><\/span>Agent Definitions and Task Workflows<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>In more advanced agentic frameworks, an <code>agents\/<\/code> folder may exist within the <code>.claude<\/code> directory. This contains structured definitions for specific sub-agents. For example, a project might have a &quot;Testing Agent&quot; defined by a specific set of prompts and a &quot;Security Auditor Agent&quot; defined by another. These files allow the system to switch between specialized roles without requiring the user to re-input complex instructions.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Execution_Logs_and_Telemetry\"><\/span>Execution Logs and Telemetry<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The <code>logs\/<\/code> directory provides a historical record of every interaction between the local tool and the Claude API. These logs are indispensable for debugging when an AI agent produces unexpected results or fails to complete a task. They capture the raw prompts sent to the model and the structured responses received, allowing developers to audit the AI\u2019s decision-making process.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Performance_Optimization_through_Caching\"><\/span>Performance Optimization through Caching<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The <code>cache\/<\/code> folder is used to store intermediate results and expensive computations. If the AI has already analyzed a large library or performed a complex calculation, the results are stored here to speed up future interactions. This reduces latency and minimizes the number of API calls, leading to a more responsive developer experience.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_Operational_Lifecycle_How_the_Folder_Functions\"><\/span>The Operational Lifecycle: How the Folder Functions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The lifecycle of the <code>.claude<\/code> folder begins the moment a Claude-powered command is executed within a project directory. The process typically follows a predictable chronology:<\/p>\n<ol>\n<li><strong>Initialization:<\/strong> The tool checks for the existence of the <code>.claude<\/code> folder. If absent, it creates the directory structure and populates it with default configuration files.<\/li>\n<li><strong>Context Loading:<\/strong> Before sending a request to the Anthropic API, the tool reads from <code>config.json<\/code> and the <code>memory\/<\/code> folder. It gathers the necessary context to make the prompt as accurate as possible.<\/li>\n<li><strong>Task Execution:<\/strong> The AI performs the requested work. If it is a multi-step process, the tool may write intermediate &quot;checkpoints&quot; to the folder to ensure that progress is not lost if the process is interrupted.<\/li>\n<li><strong>State Update:<\/strong> Once the task is complete, the tool updates the logs, refreshes the cache, and potentially updates the memory files with new information learned during the session.<\/li>\n<li><strong>Persistence:<\/strong> The folder remains in the directory, ready to provide continuity for the next command, whether it occurs seconds or days later.<\/li>\n<\/ol>\n<h2><span class=\"ez-toc-section\" id=\"Data_Efficiency_and_Cost_Implications\"><\/span>Data Efficiency and Cost Implications<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>One of the primary benefits of the <code>.claude<\/code> folder is its impact on cost management. API usage is billed based on &quot;tokens&quot;\u2014units of text processed by the model. Without the local state management provided by the <code>.claude<\/code> folder, developers would often find themselves repeating context in every prompt to ensure the model has enough information to act correctly.<\/p>\n<p>By utilizing local caching and structured memory, these tools can reduce the &quot;input token&quot; count significantly. Supporting data suggests that efficient context management via local state can reduce API costs by 30% to 50% in large-scale projects by preventing the redundant transmission of static codebase information. Furthermore, by storing &quot;embeddings&quot; (mathematical representations of text) locally, the system can perform local searches to find relevant code before ever contacting the cloud, further optimizing performance.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Security_Protocols_and_Management_Best_Practices\"><\/span>Security Protocols and Management Best Practices<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The convenience of the <code>.claude<\/code> folder brings with it several security and project management challenges. Because the folder can contain sensitive information\u2014including snippets of proprietary code, internal documentation, and occasionally API-related metadata\u2014proper handling is essential.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"The_gitignore_Mandate\"><\/span>The .gitignore Mandate<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The most critical best practice is to add <code>.claude\/<\/code> to the project\u2019s <code>.gitignore<\/code> file. In almost all scenarios, this folder represents local state that is specific to an individual developer\u2019s machine and session. Committing this folder to a shared repository like GitHub can lead to &quot;repository bloat&quot; and, more seriously, the accidental exposure of sensitive telemetry or private configuration.<\/p>\n<figure class=\"article-inline-figure\"><img src=\"https:\/\/www.kdnuggets.com\/wp-content\/uploads\/How-the-claude-folder-actually-works-01.png\" alt=\"Breaking Down the .claude Folder\" class=\"article-inline-img\" loading=\"lazy\" decoding=\"async\" \/><\/figure>\n<h3><span class=\"ez-toc-section\" id=\"Data_Privacy_and_Log_Management\"><\/span>Data Privacy and Log Management<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Developers must be aware that the <code>logs\/<\/code> directory within <code>.claude<\/code> may contain plain-text records of sensitive data processed during an AI session. In corporate environments with strict data privacy requirements, it is recommended to periodically purge these logs or use tools that support encrypted local storage.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Resetting_the_AI_State\"><\/span>Resetting the AI State<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>When an AI agent becomes &quot;confused&quot; or begins producing hallucinated results, it is often due to corrupted or outdated context stored within the <code>.claude<\/code> folder. In such cases, deleting the folder is a safe and effective troubleshooting step. Upon the next command execution, the tool will recreate the folder with a clean state, effectively &quot;rebooting&quot; the AI\u2019s local memory.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Broader_Impact_on_the_Software_Development_Life_Cycle_SDLC\"><\/span>Broader Impact on the Software Development Life Cycle (SDLC)<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The normalization of the <code>.claude<\/code> folder signals a broader evolution in the SDLC. We are moving toward a future where &quot;Project State&quot; includes not just the source code and the git history, but also the &quot;AI Context State.&quot; <\/p>\n<p>Industry analysts suggest that as these tools mature, the way we share project context among teams may change. While the <code>.claude<\/code> folder itself should remain local, the <em>definitions<\/em> of the agents and the <em>structured prompts<\/em> it contains might eventually be version-controlled in a sanitized format. This would allow teams to share &quot;AI coding standards&quot; as easily as they currently share linting rules or formatting configurations.<\/p>\n<p>Furthermore, the existence of this folder highlights the increasing importance of local-first AI. By keeping the working state on the developer\u2019s machine rather than in a centralized cloud database, developers maintain a higher degree of sovereignty over their data and their workflow. It represents a middle ground between the total privacy of local LLMs (which may lack the reasoning power of Claude) and the convenience of cloud-based AI.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The <code>.claude<\/code> folder is more than a byproduct of modern AI tooling; it is a foundational component of the next generation of software development. By providing a dedicated space for configuration, memory, and logs, it enables Claude to function as a sophisticated, context-aware collaborator rather than a simple text generator. <\/p>\n<p>As developers continue to integrate AI more deeply into their daily routines, the ability to inspect, manage, and secure the <code>.claude<\/code> directory will become as routine as managing a <code>.env<\/code> file or a node_modules folder. Embracing this local state management is the key to unlocking the full potential of agentic AI, ensuring that every interaction with the model is faster, smarter, and more aligned with the specific needs of the project at hand. In the rapidly changing landscape of artificial intelligence, the <code>.claude<\/code> folder stands as a testament to the need for persistence in an increasingly automated world.<\/p>\n<!-- RatingBintangAjaib -->","protected":false},"excerpt":{"rendered":"<p>As the integration of Large Language Models (LLMs) moves from browser-based interfaces into local development environments, developers are increasingly encountering a new artifact in their project directories: the .claude folder.&hellip;<\/p>\n","protected":false},"author":1,"featured_media":5502,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[361],"tags":[364,362,345,365,1107,712,1109,1108,1110,363,1055,549,1111,656],"class_list":["post-5503","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-artificial-intelligence-tech","tag-ai","tag-artificial-intelligence","tag-claude","tag-data-science","tag-decoding","tag-development","tag-essential","tag-folder","tag-guide","tag-machine-learning","tag-management","tag-modern","tag-state","tag-workflows"],"_links":{"self":[{"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/posts\/5503","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/comments?post=5503"}],"version-history":[{"count":0,"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/posts\/5503\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/media\/5502"}],"wp:attachment":[{"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/media?parent=5503"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/categories?post=5503"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/drcrypton.com\/index.php\/wp-json\/wp\/v2\/tags?post=5503"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}