According to @bcherny, developers can create custom agents in Claude Code by adding .md files to .claude/agents, enabling per-agent names, colors, tool sets, pre-allowed or pre-disallowed tools, permission modes, and model selection; developers can also set a default agent via the agent field in settings.json or the --agent flag, as reported by the tweet and Claude Code docs. According to code.claude.com, running /agents provides an entry point to manage sub-agents and learn more about capabilities, which streamlines workflow routing and role specialization for coding tasks. According to the Claude Code documentation, this supports enterprise use cases like policy-constrained code changes, safer tool invocation, and faster task handoffs within developer teams.

According to AnthropicAI on X, nonprofits on Anthropic’s Team and Enterprise plans now get access to Claude Opus 4.6 at no additional cost, positioning the company’s most capable model for mission-driven use cases such as policy research, grant writing, data synthesis, and multilingual knowledge retrieval (as reported by Anthropic’s post on February 9, 2026). According to Anthropic’s announcement, removing paywalls for Opus 4.6 can lower model evaluation and deployment costs for NGOs while enabling advanced capabilities like long-context reasoning, tool use, and structured outputs for program monitoring and evaluation. As reported by Anthropic’s official tweet, this move expands enterprise-grade frontier AI tools to the nonprofit sector, creating business opportunities for ecosystem partners—system integrators, data platforms, and LLM ops providers—to deliver tailored solutions like secure document pipelines, retrieval augmented generation, and governance workflows for compliance and impact reporting.