Skip to main content
Fire Agent ships with two built-in web pages served by the agent itself (no internet needed). Use them to check status, diagnose and run print tests without the point-of-sale app. Both are only reachable from the same machine where the agent runs, because it listens only on 127.0.0.1 (localhost).
If you changed the port with FIRE_AGENT_PORT, use that number instead of 9100.

Prerequisites

  • Fire Agent must be installed and running (icon visible in the system tray). If it is not, see Windows installation.
  • A supported browser: Chrome or Edge 105+, Brave, Opera or Firefox 110+. See terminal requirements.
  • The agent token (FIRE_AGENT_TOKEN). On fresh installs the default is fire-agent-dev-token; in production it is the value set during installation.
Click the Fire Agent tray icon to open the information panel directly in the browser.

Test page

The test page lets you connect to the agent and print sample receipts. It is the main tool to confirm that a printer works. The interface has a left sidebar with four sections (Connection, Printers, Print, Log) and a Connect / Disconnect button in the top right.

Open the page

Open http://localhost:9100/ in the browser. The Fire Agent interface appears.

Connection

This is the section shown when the page opens.
Fire Agent test page — Connection section
  1. In the FIRE_AGENT_TOKEN field, enter the agent token. Use the eye icon to show or hide it.
  2. Click Connect (top right).
  3. The status indicator changes:
    • Connecting… (yellow): establishing the connection.
    • Connected (green): connection successful.
    • Error (red): could not connect (check that the agent is running).
  4. On a successful connection, the agent lists the printers automatically and the button changes to Disconnect.

Printers

Fire Agent test page — Printers section
  1. Click Printers in the sidebar.
  2. You see the printers detected in Windows. The default one is marked (default).
  3. Select a printer in the Select printer dropdown. The selection is saved for next time.
  4. If you connected a new printer, click Refresh to query them again.
If no printer appears, install its driver from Windows settings first, then click Refresh.

Print

This section sends test print jobs to the selected printer.
Fire Agent test page — Print section
  1. Make sure you selected a printer in the previous section.
  2. Edit the receipt content in the ESC/POS content box (it comes with a preloaded example).
  3. Use one of the four buttons:
The result of each action appears in the Log section.

Log

Shows, with a timestamp, every message exchanged with the agent:
Fire Agent test page — Log section
  • Yellow: messages sent (→) to the agent.
  • Green: successful responses (← print_ok, printers, pong).
  • Red: errors (← ERROR: …).
Use Clear to empty the log. It is the first place to check when something fails.

Receipt formatting

Inside the text box you can apply emphasis with markers: The content is centered automatically and feed lines are added at the end.

Automatic saving

The page remembers its setup in the browser (localStorage): If the token is already saved, the agent connects on its own when the page opens and lists the printers.

Information panel

The panel is a read-only view (it does not print). It summarizes the agent status and refreshes itself every 30 seconds.
Fire Agent information panel — Status section
Open it at http://localhost:9100/panel (or click the Fire Agent tray icon). The sidebar has four sections: The ↻ Refresh button forces an immediate refresh of all data. The Printers section shows the detected printers and their status as cards:
Fire Agent information panel — Printers section
The Connection section shows the URLs available to connect to the agent:
Fire Agent information panel — Connection section
The status indicator turns Offline (red) if the agent stops responding.

Light / dark theme

Both pages have a theme button (sun/moon icon) in the top-right corner. Clicking it toggles between dark and light mode, and the preference is saved in the browser.

Troubleshooting