The 100xprompt web interface and the headless server both listen on a network address you control. They bind to your local machine by default. With a couple of flags you can open the interface to other devices on your network, advertise it over mDNS, and allow extra browser origins to connect.

​
Pick a command

Both commands start the same server and accept the same network options:
CommandWhat it does
100xprompt webStarts the server and opens the web interface in your browser.
100xprompt serveStarts a headless server with no interface - ideal for scripting, the SDK, or remote access.

​
Network options

Flagserver keyDefaultDescription
--portportAuto (tries 4096, then any free port)Port to listen on.
--hostnamehostname127.0.0.1Address to bind to. Use 0.0.0.0 to accept connections from other devices.
--mdnsmdnsfalseAdvertise the server over mDNS. Enabling it defaults the hostname to 0.0.0.0.
--corscors[]Extra browser origins allowed to connect. Repeatable.
CLI flags take precedence when set. Anything you don’t pass falls back to your server configuration, then to the defaults above.

​
Choose a host and port

The server binds to 127.0.0.1 by default, which is reachable only from your own machine. To pin it to a specific port: 
100xprompt serve --port 8080
Suppose you want to reach the interface from your phone or a second laptop. Bind to all interfaces: 
100xprompt web --hostname 0.0.0.0 --port 4096
When you bind to 0.0.0.0, 100xprompt web prints both a local URL and the LAN URLs other devices can use, so you can copy the right one for your phone or a second machine. Set the same values once in your config so every web/serve run uses them:
100xprompt.json
{
  "$schema": "https://100xprompt.com/config.json",
  "server": {
    "hostname": "0.0.0.0",
    "port": 4096
  }
}
Looking up your machine’s IP every time is tedious. With --mdns, the server advertises itself on your local network so you can reach it by a friendly name instead: 
100xprompt web --mdns
Enabling mDNS binds to 0.0.0.0 automatically (unless you set a hostname yourself) and publishes the service as 100xprompt.local. mDNS is skipped when the server is bound only to loopback, since there would be nothing for other devices to find.
Tips:
  • mDNS is the easiest way to open the web interface on a phone or another laptop - no IP address to look up.
  • Pair it with a fixed --port so the address stays the same across restarts.

​
Allow extra browser origins with CORS

Browsers may connect from localhost and 127.0.0.1 origins and from trusted 100xprompt web origins out of the box. Suppose you serve a custom front end or a dashboard from another origin. Add it with --cors (repeatable) or the cors array: 
100xprompt serve --hostname 0.0.0.0 --cors https://dash.example.com --cors https://app.example.com
100xprompt.json
{
  "$schema": "https://100xprompt.com/config.json",
  "server": {
    "cors": ["https://dash.example.com"]
  }
}
Origins from the CLI and from config are combined, so you can keep a stable set in 100xprompt.json and add one-off origins on the command line.

​
Expose to a network safely

Binding to 0.0.0.0 makes the server reachable by any device that can route to your machine, and the server can read and modify files in your project and run commands. Only expose it on networks you trust, keep it off untrusted or public Wi‑Fi, and prefer a secure tunnel or VPN for access beyond your LAN. Keep cors limited to origins you control.
  • Web Interface: use 100xprompt in the browser, from your desktop or another device.
  • SDK: drive a headless 100xprompt server programmatically.
  • Security: how 100xprompt handles access, data, and trust boundaries.

Web Interface

Use 100xprompt in the browser, from your desktop or another device.

SDK

Drive a headless 100xprompt server programmatically.

Security

How 100xprompt handles access, data, and trust boundaries.