Use and Operate Apps

An Airlock app can be used through its web UI, chat, Telegram bridge, API routes, webhooks, and schedules. The app determines which surfaces it exposes.

Use the web UI and chat

Open the app’s web URL for its regular interface. Airlock routes the app under its own subdomain at slug.DOMAIN.

Open Chat when you need an action or answer that the web UI does not expose directly. Chat uses the app’s registered tools and access rules, so it works against the same app data and capabilities as the UI.

Inspect activity

Use Activity to inspect runs and builds. Runs show how the app handled prompts, routes, schedules, webhooks, and other triggers. Build history shows source deployment progress and errors.

Use this history to diagnose a failed trigger, confirm what an app did, or follow a build after an upgrade.

Lifecycle controls

App administrators can manage lifecycle from the app actions menu:

• Suspend: stops the current container. The next allowed trigger starts it again.
• Stop: prevents automatic restart until an administrator starts it.
• Start: starts a suspended or stopped app.
• Upgrade: builds and deploys a new app version.

Suspending saves idle runtime resources without disabling normal future use. Stopping is for apps that should not accept work at all.

Use the system assistant

The Airlock Assistant manages apps, bridges, connections, members, and runs through the permissions of the signed-in user. Use it for platform-level tasks that do not belong to one app.