All memos tagged #claude-code

Looking for bidirectional sync across multiple files? This guide covers a one-way single-memo flow — MythOS → local for one CLAUDE.md. For bidirectional sync (push edits back to MythOS automatically)...

This guide sets up a Memo Drafting Loop — a recurring /loop that turns the stub memos you tag into structured drafts, in your voice, landing clean in your library. It is built for any MythOS creator...

What Fork Mode Is Forked sub-agents are a Claude Code feature (introduced in v2.1) that clones the current session's full context into a child agent rather than spawning a fresh one. The fork...

A Tool in Claude Code is a typed capability the agent can invoke during a session — built-in (Read, Write, Edit, Bash, etc.), MCP-provided, or skill-provided — each governed by the permissions system...

A Hook in Claude Code is a shell command the harness executes automatically in response to lifecycle events — tool calls, notifications, prompt submission, session start or stop — without explicit...

A Worktree in Claude Code is an isolated git worktree the harness creates for an agent's file edits, spawned via isolation: "worktree" in the Agent tool to prevent parallel agents from colliding on...

settings.json in Claude Code is the configuration file at ~/.claude/settings.json (or .claude/settings.local.json per-project) that controls permissions, hooks, environment variables, and MCP server...

Model in Claude Code refers to the specific Claude model the session runs on — Opus, Sonnet, or Haiku — switched via the /model slash command, with different cost, latency, and context window...

Compaction in Claude Code is the harness's automatic summarization mechanism that compresses earlier conversation content when the session's token usage approaches the model's context window limit,...

Auto Mode is a Claude Code permission system that uses AI classifiers to approve safe actions automatically and block dangerous ones, sitting between manual approval of every step and fully...

Headless Mode in Claude Code is the non-interactive invocation pattern triggered by claude -p "<prompt>", designed for scripting, CI pipelines, and automated agent workflows that run without a human...

Permissions in Claude Code are granular allow / ask / deny rules declared in settings.json that control which tools, Bash commands, and MCP calls run without prompting the user for approval. How Do...

A Skill in Claude Code is a file-based capability with YAML frontmatter that the harness loads on demand, exposing reusable workflows the agent can invoke by name when their description matches the...

AGENTS.md in the Claude Code and Codex context is a markdown instruction file — analogous to CLAUDE.md as Infrastructure — that cross-tool agents read at session start, enabling shared project...

The complete feature surface of Claude Code, organized by Anthropic's own documentation categories and compiled from its published docs. Features with a dedicated memo link to it; the rest are listed...

Claude-Mem is an open-source Claude Code plugin that provides persistent session memory by deploying a dedicated observer AI that watches coding sessions and captures structured observations in real...

The new rules of context engineering for Claude 5 generation models are six then/now shifts moving agent Context Engineering away from prescriptive scaffolding and toward judgment, interface design,...

CLAUDE.md is Claude Code's project-level instruction file — a Markdown document that loads into every session's context window and steers agent behavior for that project. It lives at the root of a...

If you've got an Obsidian vault full of notes and you're using Claude Code, the obvious question is: can Claude just read all of this? Yes. And it's easier than you'd think. The connection runs...

Claude Code exposes its controls as slash commands typed at the start of a message; typing / alone lists everything available in the current build. Availability varies by plan, platform, and Command...