OpenMake
ENKOJAZHDE
Live Demo
5 min read

Weekly development log 2026‑W38: Turn a fixed core into an add-on platform · partial week

As of the September 20 GitHub main snapshot, W38 has 86 commits and 34 tagged releases from 1.64.0 through 1.80.0. The main thread was a shift from feature-specific wiring to add-ons with explicit manifests, permissions, availability, and organization scope, alongside organization controls, cost accounting, catalog operations, and a measured path for admitting models.

  • Weekly log
  • Vibe coding
  • Self-hosted AI
  • 2026-W38
W38 illustration of an add-on core connected to organization controls, permissions, cost, search, and model verification modules. Created on 2026-09-20 from the development log; this is not a product screenshot.
W38 illustration of an add-on core connected to organization controls, permissions, cost, search, and model verification modules

MAIN SNAPSHOT / EVIDENCE

This week in OpenMake

As of the September 20 GitHub main snapshot, W38 has 86 commits and 34 tagged releases from 1.64.0 through 1.80.0. The main thread was a shift from feature-specific wiring to add-ons with explicit manifests, permissions, availability, and organization scope, alongside organization controls, cost accounting, catalog operations, and a measured path for admitting models.

Period
2026-09-14 – 2026-09-20
Git commits
86
Evidence
Git history

01

What changed

As of the September 20 GitHub main snapshot, W38 has 86 commits and 34 tagged releases from 1.64.0 through 1.80.0. The main thread was a shift from feature-specific wiring to add-ons with explicit manifests, permissions, availability, and organization scope, alongside organization controls, cost accounting, catalog operations, and a measured path for admitting models.

  • Agent Tasks gained durable approval waits, enforced state transitions, a tool-call journal, plan restoration, and risk-based approval. Follow-up fixes restored router behavior after timeouts, preserved attachments, and covered browser-runner and MCP recovery (#877–#899).
  • The product added an active organization context, centralized authorization, organization sharing and policy, audit history, an admin console, cost ledgers, quota reservation, approval requests, remote MCP OAuth, HITL notifications, connector artifacts, and evaluation visibility (#909–#913, #922, #928).
  • Optional capabilities moved out of Base. Add-on Host and built-in packs established the boundary; generic manifest installation replaced pack-specific seeders; discussion, Deep Research, MCP, and Skill runtimes became add-ons with declared state, entitlements, schemas, model requirements, and enforced permissions (#937, #939, #941–#942, #950, #954).
  • Model selection became evidence-bearing through per-model declaration tables, measured probes, adoption gates, capability wiring, pack-owned routing cases, a verification runner, and a verified-model indicator (#944, #959–#960).
  • The release stream also added organization-scoped extensions, a search-provider add-on for Naver, Daum, Exa, and Tavily, a dev/staging/online environment manager with post-install SearXNG search, and CI work so SBOM generation survives dependency overrides (#946, #961–#963).

02

How this week was reconstructed

This week is still in progress. Counts and claims stop at the GitHub main snapshot of September 20, 2026, 16:54 KST (fbc0e612). Counts include release commits and use KST week boundaries; changelog release dates may use a different timezone.

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

Evidence

Back to Engineering Log