Reference

Technical reference that ships with the website.

The old website linked directly to markdown files. This rebuild keeps the practical reference inside the static site so the whole bundle can be uploaded to IONOS without losing the technical material.

Getting started

Start with the surface model, then pair.

  1. Run AutoYou on the computer you own. That machine becomes the local route for chat, Browser proxy, notes, frontends, and voice.
  2. Use the public website for orientation. The website is where docs, support, and product context live.
  3. Use the account app when sign-in or devices matter. Login, trusted devices, and optional billing live on app.autoyou.me.
  4. Pair the phone to your server. Once paired, the product flow leaves the website and comes back to your own machine.

If you need a human-readable first explanation of the split between website, account app, and local server, this is the section to send before you send any QR or OTP instructions.

Private messaging pairing

From /pair to authenticated WebRTC

  1. Send /pair through a configured messaging partner such as Telegram, WhatsApp, or Signal.
  2. Receive an /otp response containing a temporary OTP and public URL.
  3. Generate SHA256(OTP:ServerPassword) locally on the remote client.
  4. POST that hash to /auth on the temporary public URL.
  5. Receive a session ID and ICE configuration.
  6. Exchange WebRTC signaling through the temporary public URL.
  7. Relay the signaling privately to the local server.
  8. Once WebRTC is stable, the temporary tunnel can be cleaned up.
/otp
{"otp":"ABC12345","url":"https://temporary-proxy.example"}

hash = SHA256("ABC12345:ServerPassword")

In plain language: the messaging partner bootstraps the connection, the OTP proves you already know the server password, and WebRTC becomes the long-lived path.

Browser proxy

Local HTTP proxy on port 8067

The Browser path exposes a local HTTP proxy client so requests can be forwarded over the WebRTC data channel. That is what makes the Browser tab, frontends, and local pages feel like part of the same product. 

GET http://localhost:8067/proxy/health

{
  "status": "connected",
  "proxy_port": 8067,
  "webrtc_connected": true
}
  1. HTTP request hits the local proxy server.
  2. The proxy serializes the request into JSON over WebRTC.
  3. The AutoYou server processes the request.
  4. The response comes back over the same data channel.
  5. The Browser surface renders the result inside AutoYou.

Session architecture

External app IDs are not the same as internal AI session IDs.

AutoYou maps external session identifiers from WhatsApp, Signal, or web clients into internal session IDs used by the agent server and memory services. That keeps outside continuity intact while still giving the internal system one clean source of truth for context. 

External session ID -> REST API -> AutoYou session ID -> Memory storage
  • External IDs: the identifiers the source app already uses.
  • Internal IDs: the identifiers used by the AI agent runtime and memory layer.
  • Why it matters: fewer collisions, better traceability, and more stable memory behavior.

Signal QR pairing

Link Signal as a secondary device, then use Notes to Self

  1. Start the Signal CLI REST container and confirm the health endpoint is working.
  2. Generate the QR code link from the Signal pairing endpoint.
  3. On your primary Signal phone, open Settings > Linked Devices.
  4. Scan the QR code to link AutoYou as a secondary device.
  5. After linking, use Signal Notes to Self to send /pair or /autopair.

If scanning fails, adjust screen brightness or distance first. If the device limit has been reached, unlink an old device before trying again.

WhatsApp QR pairing

Use the WhatsApp Web QR flow and let the session persist

  1. Start the AutoYou server and ensure the WhatsApp client is running.
  2. Open the local admin dashboard on port 8001.
  3. Wait for the WhatsApp QR to appear.
  4. On the phone, open WhatsApp linked-device settings and scan the QR.
  5. Let the client finish authentication and store the LocalAuth session.
  6. Once ready, the service can process remote Notes to Self messages through AutoYou.

QR codes rotate. A stale code is not a product failure by itself; it usually just means the current code expired before the phone completed the scan.

Local admin dashboard

The server dashboard lives on your AutoYou computer, not on the public website.

The usual local admin surface is on http://localhost:8001. That is where you review service status, inspect QR pairing, confirm voice and browser settings, and verify the routing state of the machine.

The public website points to this section instead of hard-linking everyone to a localhost address that only makes sense on the machine actually running AutoYou.