Aide AI HTTP Server

This page explains how to use Aide with a remote AI server for team-scale agent workflows.

Use this mode when you want transcription, summaries, and agent chat to run on managed infrastructure instead of your local device.

What Remote Mode controls

When Engine Backend is set to Remote (HTTP), Aide sends AI tasks to your server:

• Live recording transcription
• Audio file transcription
• Summaries
• Agent chat
• History actions (re-summarize, re-translate, re-transcribe)

If the server is unavailable or not authorized, Aide will not start these tasks.

Before you start

Prepare these items first:

• A valid server URL (example: http://server-ip:8090 or https://your-domain)
• A valid API key file from your server administrator (if your server requires auth)
• Stable network connection between your app and the server

Setup steps in Aide

1. Open Settings.
2. Go to AI Backend.
3. Set Engine Backend to Remote (HTTP).
4. Enter Remote Base URL.
5. Import the API key file in Remote API Key.
6. Click Remote Health Check.

Expected result:

• Health check passes.
• Engine status icon turns available.

If check fails, fix URL/key first before starting any AI task.

How to confirm it is working

After setup:

• Start a short recording and confirm transcript appears.
• Generate a summary and confirm non-empty output.
• Open Agent Chat and send a short message.

If these work, remote mode is configured correctly.

For team operations, validate all three regularly so capture, eternal memory extraction, and agent reasoning stay aligned.

Engine status icon (top of app)

Aide shows an engine status indicator at the top area of the app:

• Available state: backend is reachable and authorized.
• Error state: backend is not reachable, not configured, or not authorized.

This icon is informational only.

Common errors and what to do

Remote Base URL is not configured

• Add URL in Settings > AI Backend.

Health check failed

• Confirm server is running.
• Confirm host/port and protocol (http vs https).
• Confirm this device can reach the server network.

Authorization failed

• Re-import the correct API key file.
• Confirm key has not been rotated/revoked by server admin.

Task not started because backend unavailable

• Run Remote Health Check again.
• Fix URL or API key until check passes.

API key behavior in app

Important:

• Aide reads the API key from key file under .Aide/config.
• The key is not treated as a plain text setting field.
• If the key file changes, authorization result can change immediately.

If your admin rotates keys, import the new key file in Settings.

Recommended daily workflow

1. Open app.
2. Confirm engine status is available.
3. If unavailable, run Remote Health Check.
4. Start recording, file transcription, summary, or chat only after check passes.

This avoids failed tasks and confusing partial states.

For cross-team usage, keep one approved server endpoint and key policy so everyone works against the same governed runtime.

Security notes for normal users

• Do not share your API key file.
• Do not send your key in chat or screenshots.
• If you think key leaked, ask admin to rotate key and provide a new one.