StepFun Phone Revealed: STEPX Neo, Step AOS, Amoo, and Availability

What StepFun Announced on July 13

The StepFun phone is no longer a pre-launch concept. At its July 13, 2026 event in Shanghai, StepFun presented the STEPX device brand, the Step AOS agent-native operating system, the Amoo personal agent, and a phone called STEPX Neo.

The dated sequence matters. On July 13, StepFun held the launch and displayed the device. A July 14 Caixin report on the StepFun launch documented the product names, ecosystem partners, protocol-interface approach, and unresolved mass-production status. On July 15, China Daily's account of STEPX Neo described the integrated model, operating-system, and device stack.

StepFun called STEPX Neo the world's first agentic smartphone built natively around a large language model. That wording is the company's description of its product position. The South China Morning Post launch report also presents it explicitly as a StepFun claim while placing the device in the wider competition to build AI-native hardware.

The immediate answer for readers is therefore precise: STEPX Neo has been revealed, and its named software stack has been presented. The launch reporting did not establish a retail release date or broad commercial availability. A product reveal, a working demonstration, mass production, and a phone that consumers can order are separate milestones.

For readers deciding whether this belongs to a new device category, Agentic Phone Explained: What an Agentic AI Phone Means in 2026 provides the broader definition. STEPX Neo is one specific OEM-native implementation of that idea.

How STEPX Neo, Step AOS, and Amoo Fit Together

The StepFun announcement is easier to understand when each product name is assigned one responsibility. Describing the whole system simply as an “AI phone” hides the difference between reasoning, coordination, interaction, service access, branding, and hardware.

StepFun's models provide the language understanding and reasoning needed to interpret a request and plan what should happen. Model capability influences how well the system understands an ambiguous goal, resolves context, and handles multiple constraints. It does not alone determine which phone or service actions are available. Our Top AI Agent Models 2026: Capability Guide for Real Agents explains why model quality and product-level action scope should be evaluated separately.

Step AOS is the agent-native operating system presented by StepFun. Its role is to coordinate agent capabilities across the phone stack. That includes connecting a reasoned plan to supported device or service functions, managing the flow between steps, and presenting the resulting experience through the device.

Amoo is the personal-agent experience built from StepFun's model family and Step AOS. It is the user-facing part expected to receive requests, maintain relevant context, and coordinate supported tasks. Amoo should not be confused with the operating system beneath it or with every individual partner service it may call.

Protocol interfaces connect supported capabilities from external services. Caixin reported that StepFun named Alipay, Baidu, Meituan, JD.com, Didi, Trip.com, and Amap among its first ecosystem partners. These connections represent service paths exposed to the stack, while the precise functions available through each path depend on the implementation.

STEPX is the device brand, and STEPX Neo is the phone shown at the launch. The hardware provides the physical environment in which the models, Step AOS, Amoo, and connected capabilities come together. This vertical integration is the defining architectural signal, even while many conventional buying details remain unresolved.

What Protocol-Connected Services Can Change

Why does StepFun emphasize protocol interfaces instead of having an agent click through app screens? A structured service connection can expose named capabilities, inputs, outputs, status, and errors in a form that software can call directly. That can be more dependable than visually locating controls after every interface update.

Consider a travel request. A visual agent might open an app, search the screen, fill several fields, and interpret the displayed results. A protocol-connected service could instead accept structured details such as origin, destination, date, and passenger count, then return matching options and a defined status. The agent still needs to understand the request and present the choices, but it does not have to infer every interaction from pixels.

This approach is related to the wider shift covered in App Intents and Machine-Callable Apps for AI Agents. Applications become more useful to agents when they publish supported actions with clear parameters and outcomes. Structured access can also make partial failures easier to identify because the service can return a specific error rather than leaving the agent on an unexpected screen.

Protocol access and GUI operation remain different tools. A protocol can expose only the capabilities a service chooses to publish. GUI interaction may reach visible functions that lack a structured interface, but it has to cope with layout, language, account, and app-state changes. A complete phone agent may need supported paths for both, plus a practical handoff when neither route can finish the task.

The partner list does not by itself define the full action catalog. Each service may have its own account requirements, regional scope, transaction rules, data permissions, and confirmation steps. A payment, booking, order, ride request, or account change should present the consequential details and obtain the applicable user authorization before commitment.

The reported StepFun and Alipay partnership is a post-launch ecosystem signal, not a substitute for a documented capability matrix. Buyers need to see which Alipay-related actions are supported, how account identity is established, where confirmation appears, and what result is retained after a transaction attempt.

STEPX Neo: Confirmed, Claimed, and Still Unknown

Readers searching for StepFun phone specifications and availability need three separate buckets. Confirmed launch facts describe what was presented. Attributed claims state what StepFun says the system can do. Unknowns identify the information still needed before a normal purchase decision can be made.

This matrix avoids two opposite errors. The phone should not be described as merely rumored after its public reveal, but the reveal should not be expanded into specifications or availability that StepFun did not establish. The useful status is “announced and demonstrated, with key commercial details unresolved.”

How to Test the StepFun Phone on Real Tasks

Launch demonstrations show a product direction; a buyer test should reveal how the stack behaves when a task changes or fails. When hands-on demonstrations or retail units become available, begin with a multi-step request that has a clear, low-risk outcome, such as comparing travel options or preparing an order without placing it.

First, inspect how Amoo converts intent into a plan. Does it identify missing details before calling a service? Can the user correct a date, merchant, destination, or preference without restarting? A capable model should reason about the goal, while Step AOS should keep the task state understandable as supported services are invoked.

Progress visibility is the next test. The phone should communicate which service is active, what information has been supplied, which result came back, and what remains. A protocol response may be structured internally, but the user still needs a clear account of the action being prepared.

Then interrupt the workflow. Ask Amoo to stop, change one constraint, or return to a previous choice. A useful system should distinguish cancellation from completion and preserve enough context to continue safely. If one partner service fails, the interface should show whether the whole task stopped, an alternative path is available, or a manual step is required.

Sensitive actions require a direct test of confirmation. Before a payment, booking, order, message, ride request, or account change, check whether the final merchant, amount, recipient, destination, and other consequential details are visible. Confirmation should bind to those details rather than to a vague earlier request.

Finally, inspect the evidence left behind. A successful task should produce a useful result such as a booking reference, order status, route, saved draft, or receipt. An uncertain result should be labeled as pending or incomplete rather than presented as success. AI Agent Identity, Permissions, and Audit Trails: The Safety Stack Phone Agents Need explains the wider recordkeeping and recovery questions buyers should apply.

OEM-Native Agent Stack or Configurable Android Agent?

STEPX Neo and FoneClaw represent different routes to phone agency. StepFun's approach integrates its models, Step AOS, Amoo, protocol partnerships, and STEPX hardware into an OEM-native stack. FoneClaw is a configurable-model Android phone agent that connects supported model reasoning to supported actions on compatible Android phones.

The OEM-native route can coordinate hardware, operating-system behavior, personal-agent design, and selected service interfaces as one product. Its real value will depend on the depth of those supported integrations, the range of STEPX devices, and how transparently Step AOS handles permissions, confirmation, interruption, and failure.

FoneClaw's route emphasizes model choice and supported Android action workflows. The configured model interprets the request and plans the task. FoneClaw carries out supported actions, presents visible state and results, uses the required permissions, pauses for user confirmation where the action is consequential, and provides fallback when direct user handling is appropriate.

Neither deployment route should be judged from architecture alone. Buyers should compare the exact tasks they need, which apps and services are supported, whether progress is visible, how confirmation works, and what happens after partial failure. AI Agent Phone Control: How Android Phone Agents Turn Intent Into Action provides a practical framework for that comparison.

Readers exploring configurable Android alternatives can also review Best MiClaw Alternative for Android: FoneClaw Phone Actions. FoneClaw is an independent Android phone-agent product and is not part of the STEPX, Step AOS, or Amoo stack.

What Buyers Should Watch for Next

What would turn STEPX Neo from a significant launch signal into a product that buyers can evaluate normally? The first requirement is a complete hardware specification sheet. Processor, memory, storage, display, battery, charging, cameras, radios, physical dimensions, and repair or warranty details determine whether the phone works as an everyday device as well as an agent platform.

Production and sales information comes next. StepFun needs to establish whether STEPX Neo is entering mass production, when orders will open, how much it will cost, which configurations will be sold, and whether supply is intended for consumers, developers, partners, or limited demonstrations.

Regional and channel details will define who can actually use the phone. Supported countries, languages, mobile networks, online stores, retail partners, and after-sales service are all part of availability. The ecosystem list may also vary by account and region, so each connected capability needs a dated support description.

Software documentation should explain the Step AOS update policy, security maintenance period, model update process, supported service catalog, permission controls, activity history, confirmation behavior, and recovery path. Buyers should also look for a clear distinction between on-device and network-dependent functions, including what remains available when connectivity is limited.

Finally, watch for task-level evidence rather than a longer partner list. Useful demonstrations should show complete workflows, interruptions, changed constraints, permission requests, sensitive-action confirmation, partial failure, and final result records. A named integration matters most when users can see exactly what it can do and where it stops.

STEPX Neo is now a real announced device with a named agent stack, not a rumor. The next stage is commercial and operational clarity. Once StepFun publishes specifications, availability, supported capabilities, and update commitments, buyers will be able to compare the phone on the same practical terms as other Android and agentic-phone options.