Interfaces

Interfaces 🚪

You ran python run.py, typed the address, and the page is bigger than you expected. Lots to click, no clear first move. Here's the map: only four ways into aigate, all the same app at one local address. Pick the door that fits the moment.

The screen in your browser 🖥️

Type http://localhost:8080 and the whole app is one page: a welcome screen, then providers, combos, and endpoints — named paths your tools or scripts aim at, each lockable with its own key. An endpoint is not a second port; the one real port stays the app's. Endpoints can rotate outbound traffic through a Proxy Pool — advanced, safe to skip. The same page reaches the terminal, coding tools, usage records, analytics, and settings.

A phone or laptop on your network opens it too — that's why Quick Start warns about cafés. Want a door behind its own key? Configuration and Keys shows how.

A terminal, inside the browser ⌨️

A real shell in a browser tab: many tabs, full page, true full screen, a screen that stays awake, and floating controls. Terminal walks through it.

One address your own code can call 🔁

Any program you write can call the same local address the tools use and get answers back — no browser in the middle. OpenAI API has the smallest working example.

The coding tools you already use 🛠️

Launch the tool you already reach for from inside aigate, model already set: no more stopping to ask for a key and an address. The list keeps growing. CLI Tools covers setup, including the phone route.

Which door, when 🧭

Start on the browser screen — everything else begins with adding a provider. The tools and API are there when you want them; nothing forces you to write code. And nothing loads from the internet: the only traffic out goes to the providers you chose.

---