Built Maven after using OpenClaw extensively

I've spent a lot of time experimenting with agent systems, including OpenClaw, and one thing I kept running into was that my use cases gradually drifted away from what existing frameworks were optimized for. I wanted something that could handle everyday life admin, business operations, developer workflows, and voice-first interactions from the same foundation without requiring a lot of custom glue code. That eventually turned into Maven. Maven is a free, open-source agent harness built around practical automation and deployment rather than just task execution. Some of the areas I've been focusing on: \- Native voice support \- Multi-step workflow execution \- Self-hosting \- Business and client deployments \- General-purpose automation across personal and professional use cases OpenClaw was one of the projects that influenced how I think about agent architecture, but Maven ended up taking a different direction in a few areas, especially around voice interaction and workflow orchestration. I'm curious about where other OpenClaw users have hit limitations or started building their own extensions.