Our Main Goal With Influxx Is Transitioning Completely to Native Chat

Influxx now runs on native chat. The conversation layer, where Influxx asks a clarifying question, flags a decision, or shows you finished work for review, has been rebuilt as a first-class part of every Influxx surface, from the desktop ADE to its mobile companion and Podz, replacing a side panel that used to hang off the workspace. Influxx is not turning into a chatbot. It is still an outcome-first agentic environment; the moments when it needs your judgment simply have a proper home now.

What Native Chat in Influxx Actually Means

"Native chat" is a phrase that gets stretched in a lot of directions, so it is worth being precise. In Influxx, it refers to a product and interface change. The exchanges between you and your agent, the check-ins, quick questions, follow-ups, and reviews, used to happen in a secondary panel that had its own look, its own loading behavior, and slightly different quirks depending on where you opened it. That panel is gone. The same exchanges now live directly inside each surface, designed alongside the agentic workspace rather than borrowed from somewhere else.

What native chat does not refer to is any change in how Influxx works under the hood, and ETAPX is intentionally not describing infrastructure here. The update is about what the conversation layer feels like to use. If you have spent time in Influxx, you will notice it in the first check-in you answer. If you are new, it is simply how Influxx works from now on.

Agentic Environment vs Chatbot: Why the Distinction Still Holds

Any time a tool announces better chat, people reasonably wonder whether the product is pivoting toward conversation. For Influxx, the answer is no, and the reason comes down to where the value sits.

• A chatbot's product is the conversation: You send a message, it replies, and progress depends on you supplying the next instruction.
• Influxx's product is the outcome: You explain the result you want, and Influxx plans its way back from it across as many steps as it takes, largely in the background.
• Check-ins are the exception, not the rhythm: Influxx reaches out when a choice genuinely calls for a person. It does not narrate its own progress or keep a conversation going just to fill space.
• Native chat improves the exception: The redesign touches only those decision moments. It does not add more of them.

Put simply, the conversation in Influxx is the narrow channel through which your judgment enters an otherwise autonomous process. Building that channel well does not promote it to headline status. It helps the headline, getting work finished without babysitting every step, run more smoothly.

Chat was never supposed to be the star of Influxx. It just should not be the weak spot.

The Problem With the Old Check-In Panel

Even the most capable agentic workflow has points where a human has to weigh in. A request might be ambiguous. A task might fork into two reasonable directions. A finished step might need a thumbs-up before the next one begins. Influxx has handled these moments since launch. What was missing was an interface that matched the quality of everything around it.

The previous check-in layer worked in the narrow sense: messages went out and replies came back. But it felt like a separate tool sitting next to the real one. Opening it interrupted your focus right when a task was moving nicely. And the experience shifted slightly between desktop, phone, and Pods, which made it harder to build muscle memory.

That friction grew as people trusted Influxx with bigger jobs. More ambitious work branches more often, and every branch is a check-in. A tool that excels at carrying work through dozens of steps but stumbles at the handful of moments that need you has its weak spot in the worst possible place. Engineers, Pod owners, and early mobile users raised this consistently enough that it became the obvious next fix.

Five Improvements That Come With Native Chat

Here is what changed in practical terms. Each item is a design decision rather than a technical one.

1. A single, consistent design: Check-ins, questions, and follow-ups share one look and behavior on desktop, on mobile, and inside Podz, so you learn the pattern once.
2. Part of the workspace, not next to it: Responding to a question keeps you inside the flow of the task instead of sending you to a different panel.
3. Quicker exchanges: Short clarifying questions are built to be read in a second and settled with a single tap.
4. Continuity between devices: A conversation you begin at your desk is the same conversation on your phone, with no hunting for a separate thread.
5. Dedicated review moments: When an agent completes a step and needs your opinion, that review gets its own clear space rather than getting buried.

How Native Chat Works Across the ADE, the Mobile App, and Podz

The three surfaces are used differently, so native chat was tuned for each one while keeping the same core design.

In the ADE

On desktop, the conversation layer now sits beside the agentic workspace as an equal rather than a drawer you pull out. When an agent hits a genuine fork, say a naming choice, a trade-off between two sensible approaches, or a scope question, the question appears in a space built for fast, readable exchanges. Once you answer, you are back to watching the work continue without closing anything.

In the ADE Mobile App

Mobile is arguably where native chat matters most, because that is where many check-ins actually get answered: between meetings, on a commute, or first thing in the morning when you review what ran overnight. A layout built for a desktop panel and shrunk down for a phone feels worst in exactly those moments. The native version treats the phone as a surface in its own right, and that is what turns a frustrating exchange into a ten-second answer instead of and a frustrating round of scrolling and zooming.

In Podz

Podz are dedicated workspaces for organizing separate projects. With native chat, each Pod's questions, check-ins, and reviews stay inside that Pod's own context instead of collecting in one shared inbox. If you run a Pod per client or per product, the conversation for each now clearly belongs to that Pod, in the same way the Pod's tasks already did.

Who Benefits Most From Native Chat

Everyone who uses Influxx will see the new design, but some kinds of work feel the difference more than others.

• People handing off long, multi-step tasks: The bigger the job, the more forks it hits along the way. When every fork arrives as a clean, readable question, long tasks keep their momentum instead of stalling while you hunt for the right panel.
• Anyone running several projects at once: If you manage separate Pods for separate clients or products, scoped conversations make it obvious which decision belongs to which project. That clarity matters most on busy days when context switching is already expensive.
• Mobile-heavy users: If your phone is where you catch up on overnight progress or make calls between meetings, a layout designed specifically for mobile removes most of the friction that used to make those answers slow.
• Newcomers to agentic tools: A first experience with an agentic environment can feel unfamiliar. A consistent, legible check-in design makes it easier to understand when Influxx needs you and why, which builds the habit of letting it work uninterrupted the rest of the time.
• Reviewers and approvers: If your role is mainly to sign off on what an agent produced, a dedicated review space means you can see what was done and respond without piecing the context together yourself.

The common thread is attention. Native chat does not ask more of it. It makes the attention you do give count for more.

How to Work Well With Influxx Check-Ins

Native chat makes check-ins easier to handle, but you still get the most from Influxx by working with its design rather than against it. These habits help.

1. Describe outcomes, not scripts: Tell Influxx what finished looks like. The clearer the goal, the fewer clarifying questions it needs to ask.
2. Answer check-ins promptly, even from your phone: A quick reply on mobile keeps work moving. Influxx is often waiting on exactly that one decision.
3. Treat reviews as real decisions: When a step comes back for your read, take the moment seriously. Your feedback shapes everything downstream.
4. Use one Pod per project: Keeping projects separate means each check-in arrives with the right context attached.
5. Resist turning Influxx into a chat partner: If you find yourself sending step-by-step instructions, step back and restate the outcome instead.

New to agentic tools in general? Our piece on how agentic engineering became more accessible to people new to AI on Influxx is a good starting point, and you can browse more product updates on PX Campus.

Why ETAPX Invested in a Small Part of the Product

There was an easier path available. ETAPX could have kept check-ins in a simple side panel and spent every hour on the agentic engine, reasoning that conversation is a small piece of Influxx by design. The team chose otherwise, for reasons that mirror why Influxx exists as a dedicated environment in the first place: something people rely on, even briefly, should be built well rather than merely tolerated.

There is also a trust argument. A check-in is Influxx asking for your attention. If that moment is clumsy, you start to dread it, answer it carelessly, or put it off, and any of those habits undermines the promise that Influxx interrupts you only when it matters. A clean, native check-in earns confidence that the interruption was worth it. That confidence is what allows Influxx to keep interruptions rare.

This reflects a broader ETAPX view that people should stay in charge of judgment while AI carries the scaffolding, a philosophy explored in why we encourage working alongside AI at ETAPX.

What Native Chat Means for Creators and Businesses on Whistlr

Influxx and Whistlr are separate ETAPX products, and this update does not change anything about Whistlr itself. Your Chattr feed, DMs, storefront, and campaigns work exactly as they did. Still, many people who run a business on Whistlr also juggle technical or operational projects, and two parts of this update are especially relevant to that kind of fragmented day.

• Mobile-first decisions: If your days are split between filming, going live, and running a shop, the ability to settle an Influxx decision from your phone in seconds fits the way you already work.
• Project separation: Keeping a Pod per project mirrors how you might separate campaigns in Ads Manager or products in your storefront. Context stays where it belongs.

There is also a design lesson worth borrowing. Influxx improved trust by making the moments that ask for attention clean, quick, and rare. The same principle applies to how you communicate with your own peers and customers on Whistlr: fewer, clearer asks earn better responses than a constant stream of noise. If you sell on the platform, the Whistlr business tools overview is a useful place to audit how and when you reach out.

Rollout Details and What Comes Next

Native chat is live everywhere Influxx runs today: the ADE, its mobile app, and Podz. It replaces the previous check-in experience directly, so there is nothing to switch on and nothing to configure. Past conversations and check-in records come along with you, which means looking back through a Pod's past exchanges works just as before. Only future check-ins look and feel different.

This is not the finish line. Near-term work focuses on tightening consistency even further, so a check-in in a Pod opened on a phone feels exactly as immediate as one in a desktop ADE session. The team is also refining a few interactions where careful design pays off most, such as reviewing a decision with several parts or scrolling back through a longer exchange. The agentic engine is not part of this roadmap at all; every item is about bringing the conversation layer up to the standard of the rest of Influxx.

For more on how ETAPX thinks about its Apple-focused product line, see why Influxx and Ocsidian remain Apple exclusive.

Frequently Asked Questions

Is Influxx turning into a chatbot?

Not at all. Influxx remains an agentic environment focused on outcomes: you set a goal and it carries the work across many steps, reaching out only when a decision truly needs you. Native chat redesigns those decision moments without making conversation the core of the product.

What is native chat in Influxx?

Native chat is the rebuilt conversation layer for check-ins, clarifying questions, follow-ups, and reviews. It now lives inside each Influxx surface, desktop, mobile, and Podz, with one consistent design that replaces the old secondary panel.

Will Influxx ask me more questions now?

No. How often Influxx checks in is still governed by the same rule: only when a human decision is genuinely needed. Native chat changes how those moments look and feel, not how frequently they happen.

Does native chat sync between desktop and mobile?

Yes. If you begin an exchange at your desk, you can continue that exact exchange on your phone, and the reverse. You do not need to find a separate thread on each device.

How does native chat work in Podz?

Each Pod keeps its own check-ins, questions, and reviews inside its own context. If you run several Pods for different projects, each conversation stays with the Pod it belongs to rather than mixing into one inbox.

Do I need to turn on native chat?

No setup is needed. Native chat is now simply how check-ins work in every Influxx surface, and your past conversations come along automatically.

Native chat is a modest change with an outsized effect. Influxx still does the heavy lifting and still asks for you only when your judgment matters. Now, when it does ask, the exchange feels like part of the same carefully built product rather than a detour, and that makes the whole experience easier to trust.