Weekly development log 2026‑W35: Make agent work resumable, shareable, and inspectable · partial week

01

What changed

Through the audit cutoff of August 27 at 05:08 KST, GitHub main added 59 commits. After the previous week's feature run, the work moved toward making agent work recoverable and legible: local tasks can be resumed, inspected, and shared as read-only work; a shared artifact viewer keeps published output on an isolated origin; and read-only tools can run in parallel within one turn. The same pass tightened the extension and MCP boundaries, removed mock-only administrator surfaces, stopped expired sessions from polling forever, and moved PM2 logs out of ephemeral /tmp. No new tag followed 1.33.1 by the cutoff, so this is a main-branch development snapshot rather than a new release.

• Agent work gained continuity. openmake-code can list tasks, resume local work, and show a task's result, progress log, and diff again. Queued tasks no longer become permanent orphans after a restart, resume no longer leaves an old failure reason on a successful task, and the goal-judge reason is persisted while evidence views omit control-only terminate and plan steps.
• Sharing became an explicit read-only path across the server, web, and CLI. A shared task can expose its output through an isolated-origin viewer, while the CLI and web can inspect the same task without turning the shared surface into another execution channel.
• The execution loop became more observable and efficient: read-only tool calls in one turn now run in parallel across chat, Agent Tasks, and sub-agents; local-bridge writes attach diagnostics-first tsc or py_compile results; and sub-agent activity plus shadow adoption metrics record whether delegation was actually used.
• Extensions and MCP moved from drafts toward controlled installation. External skills and plugins are adapted to OpenMake in phases, plugin bundles publish into the local gallery instead of GitHub, draft skills can be approved or rejected as groups, MCP servers can be disabled without deleting them, and remote MCP login uses Authorization Code + PKCE with dynamic registration. Global registry ownership, automatic draft-server connection, connector errors, and the stale searxng bridge reference were corrected along the way.
• The web surface became less misleading. Four mode auto-trigger toggles that duplicated behavior were removed, administrator routes now have role guards and no longer fall back to fake data, the connector table keeps its columns intact, and an expired session returns the store to guest state so approval-badge polling stops instead of retrying a dead token forever.
• The reliability pass covered the edges around those features: structured JSON parsing and long-text paths were hardened, slash-invoked skills now keep the user's language and avoid leaking into pre-search or URL analysis, the rate limiter shares counters correctly behind a proxy, and PM2 reads OMK_LOG_DIR so logs can live on a persistent volume with rotation. The local checkout also contains two additional ops-branch commits not present on GitHub main; they are excluded from this public main-branch count.

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.

This week is still in progress. Counts and claims stop at the audit cutoff of August 27, 2026, 05:08 KST.

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.