Remote

Connect to your City and chat with Agents in your browser

Remote is an open-source browser chat client for your City. Open remote.downcity.ai to use your existing Agents and conversations without installing a desktop client.

Connect to a City

  1. Ask your City owner to create a citycode: connection code using the City CLI or another compatible host. They choose a City address reachable by your browser, the allowed Agents and an expiry. Each share uses an independent credential.
  2. Send the complete connection code privately. Existing authorizations can be edited or revoked by the owner; plaintext cannot be recovered from the saved authorization summary.
  3. Paste the code into Remote's single connection-code field. Remote decodes it locally and shows the City address for you to confirm. Check that address, then click Connect. Only the authorized Agents are available.

For City running on the same computer as your browser, the HTTPS Remote site permits HTTP targets with the exact host 127.0.0.1, localhost or [::1], for example http://127.0.0.1:5314. Keep City running and allow local network access if your browser asks. The address must match the actual listener; IPv6 works only when City listens on IPv6. A loopback address always refers to the recipient's own device, so use a reachable HTTPS address when sharing access to a City on another device.

In Desktop's Settings → City Remote, the owner can save an optional Remote HTTPS address after configuring their own Tunnel or reverse proxy. New codes default to that address, or the actual local listener when empty; each code can override it. Saving or clearing only validates the URL format and does not restart City, check reachability, change existing connections or rewrite shared codes.

A connection code contains the City address and an access token. Its encoding is not encryption: anyone holding it can use the authorized Agents until it expires or is revoked. The recipient note does not bind access to that person's identity or prevent forwarding. Send codes privately and revoke an authorization if its code is exposed.

Remote connects directly from your browser to City, without forwarding through a Downcity backend. It does not read connection codes from the page URL or save connection codes or credentials. Only the non-sensitive City address may be remembered. Paste the code again after reloading or reopening the page. Saved messages and conversation history remain in your City, which is the authoritative source for conversation data.

Chat with an Agent

Remote lists conversations created for the Remote entrypoint (type: chat, kind: remote). Local main chats, Chrome chats and background work are kept out of this default list. Connection codes grant access to City; they do not create separate user accounts or bind conversation history to a code.

After connecting, select an Agent and open a saved conversation, or create a new conversation. Send a message to read the reply as it streams. You can stop a running reply and respond to interaction requests or approval prompts shown in the conversation.

If the connection is interrupted, reconnect and reopen the conversation to read its current history and status from City. Remote does not automatically resend messages after a disconnection. Check the saved conversation before sending again, since City may already have accepted your message.

Browser access requirements

The City address must be accessible from your browser's network. A private address works only when your browser can reach that network, for example through your own VPN. A domain name and DNS record alone do not create a tunnel to your City or make a private service reachable.

For a City on another device, provide a reachable HTTPS endpoint with a certificate your browser trusts. Configure the reverse proxy or Cloudflare Named Tunnel yourself and forward to City's local HTTP listener. The HTTPS Remote site requires HTTPS for non-loopback targets, including private-network IP addresses. The endpoint must preserve authorization headers, support CORS preflight and forward streaming responses without buffering.

Desktop allows the browser origins https://remote.downcity.ai, http://127.0.0.1:5173, and http://localhost:5173 without additional CORS configuration. This allowlist does not provide HTTPS, a tunnel, or public network access. For a City hosted outside Desktop, configure its CORS policy to allow the Remote site's exact Origin; a Remote deployment at another address needs its own allowed Origin. If connecting fails, check that City is running, the address and port are correct, and the code's authorization has not expired or been revoked. For local targets, check the browser's local network site permission. Browser network errors can also hide CORS failures; granting local network permission does not replace City's origin allowlist. Browser support and managed-device policies vary, so permitting a loopback address in Remote does not guarantee that every browser can connect.