User requests that Managed Agents fully support Claude Code's local orchestration features, such as skills with context, forking, allowed-tools, hooks, subagents with frontmatter, and CLAUDE.md layering. They propose a "harness: claude-code" option to run Claude Code CLI headlessly within Managed Agent containers, allowing for rich local orchestration in a managed cloud environment.
Managed Agents feature request — the hosting infra is exactly what I needed. Sessions, containers, async execution, file persistence. But here's the gap: I've built a production agent locally in Claude Code using skills with context: fork, allowed-tools, hooks, subagents with frontmatter, CLAUDE.md layering. None of that orchestration transfers to Managed Agents. The Managed Agents harness only honors name and description from skill frontmatter — Claude Code has 13+ fields. No hooks, no forking, no subagent .md files. The engineering blog says Managed Agents is a "meta-harness" that can accommodate different harnesses including Claude Code. So: can we get a harness: "claude-code" option when creating a session? Container boots, mounts my .claude/ directory, Claude Code CLI runs headlessly inside it. Full skill frontmatter, hooks, subagents — everything works. Right now the choice is: rich orchestration locally OR managed cloud infra — but not both. @trq212 thoughts?