u/aaronmphilip

Hey guys, I've been using this AI for building a codex remote control for Android, as there is no better way to use codex on your Android phone other than some complex stuff that you have to go through and download. Something that is very easy to do that very easily connects your codex to your Android phone and you can use it anywhere. The best part is that I am also building it in a way that there are only two modes that I'm building:

1. When your PC is completely turned on and you can use it for free
2. When your PC is turned off and you can basically go from your mobile, add in prompts and everything, even when your PC is turned off

That has appeared, and that is one that I am thinking of adding, because it already takes a lot of money to build this app version that will be super easy to install and use on your Android phones. I am thinking of building this. I am actually building it for myself right now, but if you want one, let me know in the comments and I will be scaling and building it for you guys too.

When I started building Zelyx I had a clear idea of what I wanted to make. Something that sits above all the tools a team uses and tells you what actually needs your attention today without you having to check everything manually.

Simple enough concept. Brutal to actually build.

Here's what the 4 months looked like honestly.

The first month was entirely wrong.

I built a dashboard. A central place where you could see activity across Slack, Jira, HubSpot, Linear, email, calendar. Everything in one view.

It looked impressive in demos. It was completely useless in practice.

The problem was I had built a better version of the problem I was trying to solve. Giving someone one place to see everything from 9 tools is not reducing cognitive load. It is concentrating it. You still have to scan. You still have to decide what matters. You still have to remember what's in flight. I had just made a prettier inbox.

I scrapped the entire UI after 6 weeks.

The reframe that unlocked everything.

The question I had been trying to answer was "what is happening across all your tools."

The question I should have been answering was "what actually needs you today."

Those sound similar. They are completely different products.

The first question produces a dashboard. The second question produces an intelligence layer. One shows you everything. The other decides for you what matters.

That shift changed every single decision after it. The product stopped being about visibility and started being about filtering. Not what is in your tools but what deserves your attention out of everything in your tools.

The hardest technical problem.

Connecting to 9 different tools sounds like plumbing. It is partly plumbing. But the real hard problem is what you do after you have the data.

Every tool has its own data model. A Slack message and a Jira ticket and a HubSpot deal are completely different objects. Making them talk to each other required building what I ended up calling a canonicalization layer. Something that takes a Slack thread, a Jira issue, a calendar event, and an email chain and figures out they are all about the same piece of work.

That cross-tool linking is where most of the intelligence lives. Without it you just have 9 separate streams of data. With it you start to see things none of the individual tools can see. A commitment made in Slack that has no corresponding Jira ticket. A deal in HubSpot that hasn't had a touchpoint in 18 days while the Slack conversation about it went quiet 12 days ago. A meeting outcome that generated three separate follow-up threads across two tools with no single owner on any of them.

None of those signals exist inside any individual tool. They only exist in the space between tools.

What I used to build it.

Lovable for the frontend and initial structure. Supabase for the backend with row-level security per tenant. OAuth 2.0 for all integrations. Codex for feature work on the existing codebase. AI coding tools cut my solo build time significantly but the hardest parts, the intelligence logic, the state detection, the silence modeling, those required thinking that no tool could shortcut.

Where it is now.

Zelyx has three surfaces. Today answers "is there anything I need to care about right now." Remembering answers "what am I holding in my head that shouldn't be there." Ownership Center answers "what is not moving forward and who owns it."

It connects to Slack, Teams, Jira, Linear, HubSpot, Zendesk, Google Calendar, Outlook, and GitHub. It detects commitments made in conversation, models silence as a signal, surfaces ownership gaps, and lets you take action without leaving the operational layer.

The post from last week about the commitment detection feature got a response I didn't expect. A lot of you said you'd built or experienced something similar. Curious what the hardest cross-tool or cross-system problem has been for anyone else building in this space.