Agentic Appby Rock Studio

Agentic App

A little help, right here.

Connection basics, answers to common questions, and a direct line to Rock Studio.

Let’s get you back to it.

Questions, connection trouble, or something that doesn’t feel right? Email the studio behind Agentic App.

Email support

Need a server? Start with Agentic Server.

Agentic Server is the server setup companion to Agentic App. It provides instructions and scripts to run your own Codex app-server, with an authentication proxy and a multi-worker Docker Compose example.

  1. Choose your setup.The Codex guide covers a standard install and an advanced runtime setup for Linux x64, with prerequisite helpers for Ubuntu 24.04. The Docker example runs a proxy and two Codex workers with separate persistent storage.
  2. Configure access to your server.Set up Codex authentication for your account. For remote connections, follow the authentication proxy guide, set a non-empty access token, and provide TLS for a wss:// endpoint. Replace sample tokens before exposing the service.
  3. Add the endpoint to the app.Use your reachable proxy address and its configured authentication. Agentic App then connects to the server you operate.

The repository keeps the full installation and configuration instructions. Agentic Server is self-hosted software; it is not a hosted service or an included model subscription.

Connect your first server

Agentic App is a client for an existing agent server. Codex app-server is the current supported backend; you supply the server and its model access.

  1. Have your server address ready.Use an address reachable from the device running Agentic App, plus any authentication required by your server. For the hosted web app, use a secure wss:// endpoint.
  2. Add it in Agentic App.Choose Add server on the empty screen, or add a server from Settings. Enter the endpoint and choose Save.
  3. Connect and start a conversation.If no server is active, saving attempts to connect. Otherwise, use the server switcher or Settings to select the server you want.
Local Codex setup example

With Codex installed and configured, this starts an app-server on the same computer:

codex app-server --listen ws://127.0.0.1:4500

Connect a native client on that computer to ws://127.0.0.1:4500. The loopback address is not reachable from another device. For the hosted HTTPS web app or remote access, provide an appropriately secured endpoint, typically through an authenticated WSS proxy. Do not expose an unauthenticated agent server to the public internet.

Common questions

Why can’t I connect?

Check that the server is running and that the address is reachable from this device. Confirm the port, authentication, and supported API version. A VPN, firewall, or proxy can also affect the connection. When using the hosted web app, use WSS; browsers can block insecure WebSocket connections from an HTTPS page.

If it still fails, email the error message with credentials and private information removed.

Does the app include an agent server or model access?

Agentic App provides the interface and does not bundle a server or model access. The separate Agentic Server project helps you set up your own server. You or your server operator manage agent execution, model access, tools, and storage.

Can I use more than one server?

Yes. Save multiple servers and switch between them from the server switcher, the desktop Servers menu, or Settings. Adding a server does not replace an already active connection automatically.

Which agent backends are supported?

Codex app-server is the current supported backend. The app is designed to accommodate more agent APIs, but you should not assume compatibility with Copilot, Claude Code, or another server until support is announced.

Where are my conversations and files?

The server stores the agent’s conversations and files. The app saves UI preferences and server connection settings on your device. Files you explicitly download or export are also saved where you choose. Removing the app does not delete data on your server. Read the privacy policy for details.

Who handles server or model problems?

Contact us about the app’s interface or connection behavior. For server outages, model-provider billing, credentials, or server data recovery, contact your server operator or the relevant provider.

Help us understand what happened

A useful bug report includes:

  • Your device, operating system, and app version.
  • The server API and version you’re connecting to.
  • What you expected, what happened, and how to reproduce it.
  • The error text or a screenshot with private information removed.

Please remove passwords, API keys, access tokens, private conversations, and credentials embedded in server URLs before sending. Support email is handled as described in our privacy policy.