Tracemoor

Remote access to a session

Remote access lets a second machine in your network follow a running chat session in a browser and answer it. Use it when the AI works for a long time on one machine, for example while it operates an app there, and you want to keep an eye on it from another device.

The other machine sees the conversation and can type replies into the session. It cannot start sessions: only sessions that are running in Tracemoor are offered. Remote access works with Claude (CLI) sessions in subscription mode.

A reply from the other machine is typed into claude on this machine. It can make claude run commands with your keys and your Git access. Keep remote access within your own network, allow only machines you control, and turn it off when you do not use it.

Set up remote access

  1. Choose AI › Remote Access…. Preferences opens on the Remote Access tab.
  2. Under Bind address, choose one network interface and enter the port. Loopback is the right choice for a first test: nothing outside this machine can connect.
  3. Under Allowed peers (one IP per line), enter the IP address of the other machine. An empty list admits nobody. Entries that are not valid IP addresses are ignored. Give the other machine a fixed address.
  4. Under Access token, click Regenerate to create a token. The token authenticates the other machine. The peer list only filters.
  5. Tick Enable remote session access and click Start.
  6. Open the link under Open this on the other machine in a browser there. The link carries the token. The page removes it from the address bar after loading.

Stop ends the server. Regenerate makes the old token invalid at once.

Get notified when the AI waits

Under Notify when a session needs input, enter a URL that accepts a plain POST request, for example an ntfy, Gotify or Pushover topic. Tracemoor sends one request when a session starts waiting for you, not on every check. Leave the field empty to turn this off.

The detection runs in the Tracemoor window. With the window closed, the conversation and replies keep working, but no notification is sent and the waiting state on the remote page is marked as outdated.

Audit

Every reply from a remote machine is recorded before it is written into the session. Write audit › Show lists these entries.

Limits

  • Traffic is not encrypted. On a network you do not control, treat the conversation as readable by others. It contains your source code and your prompts.
  • The server listens on one interface only, never on all of them.