Category Archives: Anthropic

Claude Code headless mode—now documented as running Claude Code programmatically or non-interactively—lets scripts, CI jobs, cron tasks, pre-commit hooks, and batch workflows invoke Claude without an interactive terminal session. The central interface is claude -p, which accepts a prompt, reads stdin where useful, returns output to stdout, and supports machine-readable output formats, structured JSON schemas, […]

Claude Code hooks are deterministic automation points that run when specific events occur in a Claude Code session. Current Claude Code documentation supports command hooks, HTTP hooks, MCP-tool hooks, prompt hooks, and agent-based hooks across lifecycle events such as SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, PostToolUse, SubagentStart/Stop, WorktreeCreate/Remove, PreCompact/PostCompact, ConfigChange, FileChanged, and SessionEnd. Within Claude Engineering, hooks […]

Claude Code security reviews combine semantic code analysis with the repository context Claude already uses for software development. Current Anthropic tooling includes the /security-review command for on-demand review, an official GitHub Action for pull-request review, and a newer Claude Security capability in public beta for Enterprise users. These tools look for vulnerability patterns such as […]

Claude Code subagents are separate agent instances that handle focused subtasks in their own context windows and return results to the main conversation. Current Claude Code includes built-in Explore, Plan, and general-purpose subagents and lets teams define custom agents as Markdown files with YAML frontmatter controlling name, description, tools, model, permission mode, skills, hooks, memory, […]

Claude Code test generation is most effective when the task starts from behavior and existing test conventions rather than “increase coverage.” Current Claude Code workflow documentation recommends identifying untested code, generating scaffolding, adding meaningful edge cases, then running the tests and fixing failures. Claude examines existing test files to match framework, style, fixtures, and assertion […]

Claude Code worktrees let developers run isolated sessions against separate Git checkouts so concurrent tasks do not edit the same working tree. Current Claude Code supports claude –worktree name, worktree isolation for subagents, sparse worktree paths for large repositories, and hook events around worktree creation/removal. This makes worktrees a practical boundary for parallel implementation, risky […]

Claude computer use workflows let an API application give Claude screenshot, mouse, keyboard, and desktop interaction capabilities inside an environment the application controls. Current Claude Platform documentation defines the computer_toolset_20260801 client toolset on supported Claude API/Google Cloud models, providing member actions such as screenshot, click, type, scroll, key presses, and zoom through structured tool calls. […]

Claude context editing is an API feature for selectively removing old content from conversation history before the prompt reaches Claude. Current Claude Platform guidance positions it as one of several context-management techniques alongside server-side compaction, prompt caching, tool search, and programmatic tool calling. Context editing is most useful for long-running agent workflows where accumulated tool […]

Citations make enterprise search answers easier to verify, but they do not fix weak retrieval. Anthropic’s Claude API can return citations that point to source passages from documents, and search-result content blocks can carry source attribution for retrieval-augmented generation. Those features are useful when users need to see why an answer is supported. The quality […]

Claude Code can participate in CI workflows in two different ways: as an interactive collaborator triggered from issues and pull requests, or as an automated worker launched by a GitHub Actions event. Anthropic’s official GitHub Action packages Claude Code for this environment, but the surrounding workflow still determines what code it can read, what it […]

“Custom commands” is still a useful way to think about repeatable Claude Code workflows, but the current product model is broader: Anthropic has merged custom commands into skills. Existing Markdown files under .claude/commands/ continue to work, while new reusable workflows are generally better created as skills under .claude/skills/<name>/SKILL.md. Both can create slash-invoked behavior such as […]

Engineering with Claude is less about finding one perfect prompt and more about designing a dependable system around a probabilistic model. A production application has to decide what Claude may see, which tools it can call, how state is carried across turns, what happens when an API request fails, how much a run may cost, […]

A production agent loop is not simply a model call repeated until the answer looks finished. It is the control system that decides when Claude can inspect data, call a tool, change state, ask for input, recover from failure, and stop. The Anthropic Agent SDK matters because it packages the same general agent machinery used […]

Reliable Claude API integrations treat errors as part of the protocol, not as exceptional surprises. The practical question is not whether a request can fail, but whether the application can tell the difference between a malformed request, a permission problem, a rate limit, a temporary service condition, and a failure that happened after a streaming […]

Idempotency becomes important the moment a Claude-powered workflow can be retried. A network timeout, worker restart, queue redelivery, or user double-submit can cause the same logical job to reach the application more than once. If the workflow only generates text, that may produce duplicate cost or duplicate output. If the workflow can call tools that […]