oh-my-agent: cross-vendor scheduling, Kimi and OpenCode land The oh-my-agent project merged 135 commits this week, adding Kimi and OpenCode as new vendors and introducing an OS-level scheduler that allows agents to run on a timer rather than only on demand. The cross-vendor harness now supports scheduling via launchd, systemd, crontab, and Windows schtasks, with natural-language interval specification. Other improvements include new agent roles, mobile framework support, faster hook invocation, and removal of the sunsetting Gemini CLI. Two new vendors and an OS-level scheduler merged into oh-my-agent this week, which means your agents can now run on a clock instead of only when you prompt them. 135 commits, and the theme underneath most of them is the same: stop pinning the agent to a single runtime, and stop leaking resources between sessions. oh-my-agent is a cross-vendor harness. The point is that a workflow, a skill, or a subagent dispatch should not care which CLI is underneath it. This week pushed hard on that promise. KIMI API KEY auth, TOML hook install into ~/.kimi-code/config.toml , mode-aware Serena and chrome-devtools MCP, and external dispatch via kimi -p . opencode run --agent