Duplicate check
Context / Summary
Omac serve bypasses skill checks
Problem / What
When using omac via omac serve and the opencode gui. It is possible to have a session that does not have all skills active. This is highly detrimental, especially in complex agent setups where an agent may just take it as given (with some justification) that it is supposed to code without tests.
Suggested fix / Ask
Perform the skill readiness check every time a session gets spun up.
Non-goals
No response
Evidence / Environment
Env: local development with wsl (NAT network setup)
Evidence:
Excerpt from an omac session, printed at its end.
Environment blockages (NOT code failures) — surfaced for host action
Throughout this run, several omac skills were BROKEN / not host-approved, blocking runtime verification inside the sandbox:
gradle skill not host-approved → backend unitTest/integrationTest could not execute. Static reviews passed; runtime pass/fail is unverified.
stack skill not host-approved → fullstack could not start → runtime E2E execution blocked for all scenarios. E2E tests were authored + reviewed (APPROVED) during Loop 2; only the live run is blocked.
<skill omitted>, <skill omitted>, <skill omitted>, <skill omitted> skills also BROKEN (not used in this run).
npm registry sandbox-blocked → bun install failed in fresh worktrees (worked around via pre-existing node_modules where possible).
To unblock runtime verification on the host, run from a host terminal outside the sandbox:
omac register gradle
omac register stack
Duplicate check
Context / Summary
Omac serve bypasses skill checks
Problem / What
When using omac via omac serve and the opencode gui. It is possible to have a session that does not have all skills active. This is highly detrimental, especially in complex agent setups where an agent may just take it as given (with some justification) that it is supposed to code without tests.
Suggested fix / Ask
Perform the skill readiness check every time a session gets spun up.
Non-goals
No response
Evidence / Environment
Env: local development with wsl (NAT network setup)
Evidence:
Excerpt from an omac session, printed at its end.
Environment blockages (NOT code failures) — surfaced for host action
Throughout this run, several omac skills were BROKEN / not host-approved, blocking runtime verification inside the sandbox:
gradle skill not host-approved → backend unitTest/integrationTest could not execute. Static reviews passed; runtime pass/fail is unverified.
stack skill not host-approved → fullstack could not start → runtime E2E execution blocked for all scenarios. E2E tests were authored + reviewed (APPROVED) during Loop 2; only the live run is blocked.
<skill omitted>,<skill omitted>,<skill omitted>,<skill omitted>skills also BROKEN (not used in this run).npm registry sandbox-blocked → bun install failed in fresh worktrees (worked around via pre-existing node_modules where possible).
To unblock runtime verification on the host, run from a host terminal outside the sandbox:
omac register gradle
omac register stack