oh-my-agent: strict commit attribution and capability routing

The oh-my-agent project introduced a commit-msg hook that enforces exact Co-authored-by addresses for agent commits, ensuring correct GitHub attribution. The update also routes capabilities more strictly, adds blanket permissions for Claude and Qwen to reduce confirmation prompts, and optimizes memory by sharing Serena configuration at the bridge daemon. The project targets teams that orchestrate multiple AI agents.

When you tell an agent to write code, getting it to commit with the right attribution is surprisingly brittle. A typo in a co-author address survives a history rewrite and ruins contributor graphs forever. This week, we fixed that and tightened up how capabilities are routed across the system. commit-msg hook to enforce exact Co-authored-by addresses, guaranteeing correct GitHub attribution for agent commits. oma and ls blanket permissions for Claude and Qwen, cutting down on repetitive confirmation prompts during long runs.The git hook checks against your allowed addresses before the commit writes to disk. If you already use husky or lefthook , it politely provides the one line you need to add instead of taking over your configuration. serena configuration at the shared bridge daemon, saving memory by preventing duplicate server processes per session. pi and opencode extension vendors in the default linking path so they generate and document correctly out of the box. 023 handles the transition automatically. macOS / Linux curl -fsSL https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.sh | bash Windows PowerShell irm https://raw.githubusercontent.com/first-fluke/oh-my-agent/main/cli/install.ps1 | iex oh-my-agent is built for teams who orchestrate more than they prompt. Next up: expanding capability discovery across distributed teams.