Influxx Native Chat: Why Your Agent's Check-Ins Finally Have a Proper Home

Influxx native chat is a rebuilt conversational layer for the moments when your agent needs you: clarifying questions, decisions at a fork, quick follow-ups and reviews of finished steps. It is now built directly into the ADE, the ADE mobile app and Podz as one consistent experience, replacing the side panel that used to host those exchanges. Influxx itself works the way it always has. You describe an outcome, the work runs across as many steps as it needs, and you're pulled in only when a real decision calls for your judgment. What's different is that those moments now feel like part of the product instead of a detour away from it.

We know how “native chat” sounds out of context, so a good part of this piece is about what it isn't. But first, the problem it solves.

What is Influxx native chat?

Every agentic workflow, however autonomous, has a handful of moments that need a person. Influxx has always had them. Before committing to one reading of an ambiguous request, it asks. When a task branches into genuinely different directions and only your judgment can pick one, it surfaces the choice. When an agent finishes a step that deserves a look, it shows you the result and waits for a thumbs-up, a correction or a follow-up. That exchange layer has been part of Influxx since launch.

Influxx native chat is the new interface for that layer. It isn't a new mode, a new assistant or a new way of giving instructions. It's the place where your agent's check-ins happen, rebuilt to belong to each surface you use Influxx on, and to look and behave the same on all of them.

Why an agentic workspace needs good check-ins at all

It's tempting to think that the better an agent gets, the less the conversation part matters. In practice the opposite happens. As people hand Influxx more ambitious work, tasks branch into more real decisions, and the check-in layer gets used more. The rare moments where you weigh in are also the moments where the outcome is most sensitive to what you say.

There are roughly three kinds of check-in, and each asks something different of you:

• Clarifying questions, where Influxx wants to confirm what you meant before it commits to an interpretation.
• Decisions at a fork, where two reasonable approaches exist and the choice is about your taste, your priorities or your scope.
• Reviews, where an agent has finished a step and wants your read before moving on to the next one.

A tool that's excellent across ninety steps of work but awkward at the five moments where you're asked to decide has a design problem sitting exactly where it matters most. That's the gap native chat closes.

What was wrong with the old check-in panel?

Nothing was broken, in the narrow sense. Messages sent, replies arrived. The problem was how it felt to use. The check-in layer opened as a panel next to the workspace rather than inside it, with its own visual language, its own loading behavior and its own quirks depending on where you met it. It looked a little different in the ADE on desktop than it did on the mobile app, and different again inside a Pod. Engineers told us that switching into it felt like a small context break in the middle of a task that was otherwise moving well.

We heard versions of that from engineers, from Pod owners and from early users of the mobile app, and we heard it consistently enough that it became the obvious next thing to fix. One Pod owner running separate client projects told us they used to lose track of which check-in belonged to which project, because the conversation side felt far less organized than everything around it.

What changed with Influxx native chat

This is a product and interface change. We're deliberately not describing what sits underneath it, because that isn't what changed for you. Here is what did:

Replies and reactions also feel immediate now, in a layout designed around fast back-and-forth rather than adapted from something else. None of these is dramatic on its own. Together they remove most of the small frictions that used to sit between you and a decision.

Is Influxx becoming a chatbot?

No, and we'd rather say so directly than leave it as an implication. A chatbot's job is the conversation. Influxx's job is the outcome, and the conversation is a small, necessary part of getting there: the part where your judgment plugs in. Making that part well designed doesn't make it the main event.

Native chat didn't add check-ins. It didn't make Influxx narrate its own progress, report after every step or keep a conversation going for its own sake. The frequency of check-ins is still governed by the same rule as before: Influxx surfaces a moment only when a real decision needs a human.

We didn't build a better chat window and call it the product. We looked at the few moments where Influxx actually has to ask you something and gave them a proper place to happen. The agentic core didn't move.

— The ETAPX team

How Influxx native chat works in the ADE, the mobile app and Podz

Native chat touches three surfaces, and each one is used a little differently, so each got its own tuning on top of the shared design.

In the ADE

The check-in layer now sits beside the agentic workspace as a peer rather than a drawer you pull open. Say an agent working through a multi-step engineering task reaches a naming decision, or a trade-off between two sensible approaches, or a question about scope. That question appears in a place built for a quick, readable exchange, and answering it drops you straight back into watching the work continue. You don't close one interface to get back to another.

In the ADE mobile app

Mobile is where a lot of check-ins actually get answered: a decision between meetings, a review of what an agent finished overnight, a one-line clarification typed while you're technically doing something else. A panel designed for a desktop and squeezed onto a phone shows its seams fastest in exactly those moments. The native version treats mobile as its own surface, which is the difference between a check-in that takes a few seconds and one that takes a couple of minutes of zooming and scrolling.

In Podz

Each Pod's check-ins, questions and reviews now live inside that Pod's own context instead of spilling into one shared inbox. If you run three Pods for three different projects, each one's conversation layer feels like it belongs to that Pod, the same way the work inside it already did. For anyone juggling client work, that alone removes a whole category of “wait, which project was this about?”

A working day with Influxx native chat

The clearest way to see the change is to walk through an ordinary day, because no single feature is the point. The point is how many small frictions are gone.

1. Morning: you hand Influxx a task the way you always have, by describing the result you want rather than a script of instructions.
2. An hour later, a specific question arrives about a decision the task has reached, shown in the same visual language as the rest of the ADE. You read one sentence, tap a response, and the task keeps moving.
3. Midday, away from your desk, a Pod finishes a step worth reviewing. On your phone the review is laid out for a phone screen, with the context you need to make a call. You answer, and by the time you're back at your laptop the work has moved forward on that answer.
4. Late afternoon, a second Pod raises an open-ended question where your taste matters more than the agent's competence. You settle it in a couple of messages, because the interface is built for quick exchanges.
5. Evening: you look back and realize there were no more check-ins than on any other day. They just didn't feel like interruptions.

That last step is the one we care about. Influxx still did the large majority of the work without asking anything of you. The moments where it did ask stopped being the clunky part of an otherwise smooth day.

Why better check-ins lead to better outcomes

There was a simpler path, and we considered it: leave the check-in layer as a light secondary panel and put every hour into the agentic core, on the theory that the conversational part is small by design. We rejected it for the same reason Influxx exists as its own product in the first place. Something people rely on, even briefly, deserves to be built well rather than tolerated.

There's also a trust argument that's easy to underrate. A check-in is Influxx asking for your attention and your judgment. If that moment feels clumsy, it slowly teaches you to dread check-ins, to answer them faster and less carefully than they deserve, or to put them off. Any of those undermines the promise that Influxx only interrupts you when it matters. A well-designed check-in earns the interruption, and that's what lets Influxx keep interruptions rare.

The check-in is the exact point where your judgment enters the work. If that moment is awkward, people answer it badly. We wanted it to be the easiest part of the day, not the most annoying.

— The ETAPX team

Do you need to change anything to use Influxx native chat?

No. Native chat is live across the ADE, the ADE mobile app and Podz, and it replaces the previous check-in experience outright. There's no opt-in and no separate mode to switch into. Your existing conversations and check-in history carry forward, so if you look back at a Pod's history from last month, it's all still there. Only future check-ins look and feel different.

How you use Influxx day to day stays the same: hand off an outcome, let the work run, respond when a real decision comes up. If you've built habits around reviewing on your phone or keeping Pods separate per client, those habits should simply feel lighter now.

What comes next for Influxx native chat

This isn't the finish line. The near-term work is about tightening consistency further, so that a check-in in a Pod opened on a phone feels exactly as immediate as one in a desktop ADE session. We're also giving extra design attention to the interactions that benefit most from it, like reviewing a multi-part decision or scanning back through a longer exchange.

None of that roadmap touches the agentic core. It's entirely about making the conversational layer pull its weight as well as the rest of Influxx already does. The goal was never to make chat the centerpiece. It was to stop it being the weak point.

Frequently asked questions

Is Influxx turning into a chatbot with native chat?

No. Influxx remains an outcome-driven agentic environment: you describe a goal, the work runs across multiple steps on its own, and you're asked to weigh in only when a real decision needs your judgment. Native chat redesigns the interface for those check-ins. It doesn't make conversation the main way you use Influxx or change how much of the work happens without you.

What exactly is different about Influxx native chat?

Check-ins, clarifying questions, follow-ups and reviews used to appear in a side panel that varied between the ADE, the mobile app and Podz. They're now built into each surface as one consistent design, respond faster, and carry across devices. A conversation started on desktop can be picked up on mobile without hunting for it, and reviews have their own clear place.

Will Influxx check in with me more often now?

No. Check-in frequency follows the same principle as before: Influxx surfaces a moment only when a genuine decision needs a person. Native chat didn't add check-ins, progress updates or extra questions. It changed how the check-ins that were always going to happen look and feel, so they read as part of the product rather than an interruption from somewhere else.

Does native chat work the same in the ADE, the mobile app and Podz?

It shares one design across all three, with each surface tuned for how it's used. The mobile app is built for quick exchanges on the go, the ADE places check-ins beside the work as a peer, and Podz keeps each Pod's conversation inside that Pod's context. A conversation started on one surface carries over cleanly to another.

Do I need to set anything up to get Influxx native chat?

No setup is needed. Native chat is the default check-in experience across the ADE, the ADE mobile app and Podz, replacing the old panel rather than sitting beside it as an option. Your existing conversation and check-in history carries forward, and the way you hand off outcomes and respond to decisions stays exactly the same as before.