What's next for ReacherX

Then there's an MCP server. MCP is a standard way for tools like Claude or Cursor to connect to external apps, so it would let you use ReacherX in Codex, Claude, Cursor, or another tool that supports it. I'm a developer and designer myself, and I take a lot of inspiration from Cursor. Being able to work with ReacherX from the tools you already use makes sense to me.

And I want a mobile app. You shouldn't have to sit at a computer just to pick up a conversation.

These are plans. They aren't available in v4 beta today, and I haven't promised dates for them.

There is still work to do on what's here

Finding the right people accurately has been the biggest challenge with ReacherX. Adding more ways to contact someone won't help much if the person shouldn't have been suggested in the first place.

The repository roadmap includes work on testing search results and plans. Setup, error messages, and the experience of running the app yourself also need work. I don't want to leave those things behind while adding features.

Tell me what you need

I am the only person building this right now. I can't do everything at once, and I don't think I can figure out every use case on my own either.

If you've tried ReacherX, tell me what you were trying to do and what stopped you. That could change what I work on next.

If you want to build a feature, integration, roadmap item, or change to △ Agent, get in touch first. The same applies to architecture and major UX changes. Small fixes, typos, and focused polish don't need a long discussion.

I've written about supporting development if you want to help me stay full time, and how △ Agent works if you want to get into the code.