Phase 62
Claude Code
Claude Code runs natively inside m3OS, using the supported Node, network, git, and GitHub tooling to read code, run commands, and participate in the same developer workflow the earlier post-1.0 phases made possible.
Learning goal
Understand how a modern CLI agent combines runtime, network, terminal, subprocess, and repository workflows.
Category
productivity
Components touched
Builds on
Unlocked by this phase
Why this phase matters
Claude Code runs natively inside m3OS, using the supported Node, network, git, and GitHub tooling to read code, run commands, and participate in the same developer workflow the earlier post-1.0 phases made possible.
How it works in m3OS
The roadmap entry defines the learning scope for this phase; a deeper implementation doc has not been matched yet.
How it builds on earlier phases
This phase builds on Node.js and turns that foundation into Claude Code.
Implementation outline
- Define the supported installation and launch path for the tool.
- Validate the file, shell, git, and network workflows the tool depends on.
- Document the credential-handling and support-boundary story.
- Test the supported workflows inside m3OS end-to-end.
- Update the standalone roadmap and top-level docs for the new milestone.
Task progress snapshot
No checklist tasks were discovered for this phase yet.
Documentation targets
- Documentation deliverables have not been listed yet.
Deferred follow-on work
- Extended protocol ecosystems and optional integrations
- Broader multi-user or enterprise credential-management stories
- Rich GUI integration for the agent
- Offline or local-model alternatives beyond the documented cloud-backed path
Source materials
Important code
Code spotlight cards
Code spotlight
Cargo
When the phase lands, bump kernel/Cargo.toml and any release/version references to 0.62.0.
Key files
- kernel/Cargo.toml — When the phase lands, bump kernel/Cargo.toml and any release/version references to 0.62.0.
How real OSes differ
- Mature desktop and server operating systems can support much broader agent ecosystems and integrations than m3OS should assume here.
- The real value of this phase is as a platform-integration proof point, not as a claim that m3OS has become a full hosted AI workspace.
- Explicit non-goals matter here because the surrounding ecosystem can grow much faster than the OS itself.
Success criteria
- The supported install path for Claude Code works inside m3OS.
- The tool can execute the documented file, shell, and git workflows on m3OS.
- The supported network/API path works with documented credential handling.
- The docs explicitly describe what Claude Code workflows are supported and what remains out of scope.
- The milestone can be reproduced through the documented runtime and package setup.
Related phases