Thanks for raising this and it is a fair question.

My current thinking is that it started from the idea of bringing an OpenClaw-style experience into the .NET ecosystem, but I do not see it as stopping at being just a clone or parity project. The near-term goal is to build something compatible enough to be useful for people who like the OpenClaw model, while taking advantage of .NET strengths like deployment flexibility, stronger backend integration, and a more production-oriented runtime.

Longer term, I see it evolving into its own direction rather than remaining only "OpenClaw in .NET." That means improving areas like observability, approvals/governance, desktop/local runtime scenarios, compatibility diagnostics, and a more opinionated product experience on top of the runtime.

You’re also right that some features are still missing. At this stage, I’d describe the project as being in the transition between:

1. establishing a solid OpenClaw-like foundation, and

2. growing into a broader, distinct platform.

So I’d really value discussion around two things:

which missing features people see as essential for baseline usefulness/parity

which areas feel like opportunities to go beyond OpenClaw and make this genuinely better or different

I’m very open to feedback on both, because I think the answer should probably be "both": useful familiarity first, then a clearer independent direction over time.

I've noticed a problem with the model context protocol logic in the project. I'm encountering initialization errors when using these tools in VS Code, and since this code is from Vibe Coding, I'd like to refactor this logic using the official MCP SDK and perform relevant tests. I hope you can approve this.

https://github.com/modelcontextprotocol/csharp-sdk