Start with Nexting

Start here to understand what Nexting connects, where trust lives, and which first step matches the product or hardware you have. Building a reference board is an optional developer path—not the definition of a Nexting device.

How Nexting connects

encrypted BLE → trusted Nexting Host → Agent integration

Many Nexting device forms

PIN

Ring

DIY

BLEEncrypted GATT · device ↔ Host

↔

Nexting Cloud

Identity · routing · encrypted envelopes

Trusted Host↕

Phone or computer · BLE terminates here

The cloud delivers envelopes, not Agent credentials

ENCRYPTEDHost ↔ Cloud ↔ Agent

↔

Nexting Agent integrations

One device protocol, many supported Agents

Claude Code

Codex

Grok

Cursor

OpenClaw

Arrows represent bidirectional message and state flow.

Your accessory never signs in to Claude Code, Codex, Grok, Cursor, or another Agent. It reports bounded physical intent to a trusted Nexting Host on a phone or computer. On the official path, the Nexting App is that Host; you do not install or build another one. Only developers building their own mobile, desktop, or alternative app would need a private Host implementation, which is not part of this public SDK. The official Nexting App authorizes the device, keeps credentials and sessions, and maps that intent to the selected Agent; the cloud carries encrypted envelopes and only the delivery metadata it needs.

Choose your path

First remote interaction

1. 1

   Connect the Agent

   In the Nexting App (the official Host), choose the Claude Code, Codex, Grok, Cursor, or supported Agent session you want to control.
2. 2

   Pair and authorize

   Use the product's public onboarding flow. The Host verifies device identity and declared profiles before enabling actions.
3. 3

   Trigger a mapped control

   Approve a one-time request, move a selection, or send another declared physical event; the SDK does not prescribe which physical control performs it.
4. 4

   Continue the same session

   The Host validates freshness and policy, applies the mapped action, and sends only the resulting bounded state back to the device.

Allow and Deny are protocol choices, not fixed buttons. For a MultiPad, your firmware can map any key, encoder press, or other physical control toallow or deny. The SDK defines the meaning sent over the link, not the device shape or key layout.

A first-party product can complete this path when its public onboarding supports the selected Agent. DIY hardware should first prove approval/1 with the public Host verifier; this does not require building a Host. It becomes a remote Agent control only after public developer enrollment is available.

What is a Host, and who needs to build one?

A Host is not another program users need to download or build. On the Nexting path, the official App already provides Bluetooth, device authorization, credential protection, session selection, and Agent mapping. This public SDK documents the device side; custom App/Host implementations are private product work and are not a supported installation path.

Security in one minute

The nearby link uses BLE LE Secure Connections and encrypted GATT control traffic. The Host sends minimum, bounded profile data and remains the only layer that can authorize a device action against an Agent session.

Next: choose by your goal

If you are only using a finished device, stop after installing the Nexting App and connecting it. You do not build a Host. The table below gives the single entry point for each other goal.