OpenMake
01
What changed
The busiest June week pushed execution beyond simple conversation. Task sandboxes, browser and web paths, artifact handling, attachments, MCP tooling, and chat orchestration became a connected runtime.
- Built out task-sandbox isolation.
- Expanded web, browser, and MCP execution paths.
- Improved artifacts, attachments, and chat orchestration.
02
How this week was reconstructed
No matching local Claude Code project transcript was recovered for this period. This entry therefore describes only what the Git history can prove.
We audited the available Claude Code main sessions, their proven child lineages, and the repository history. Session notes explain intent and investigation; Git remains the authority for code that actually landed.
03
Team identity and project roles
OpenMake Team is the community identity; openmake_llm is the software project; OpenMake is the product name. Non-developer maker riskpw leads openmake_llm through vibe coding, and professional developer rocky supports its development.
Source evidence