public-ingress

Configure ngrok tunnels and persist the public URL as ingress.publicBaseUrl.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill public-ingress-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: public-ingress
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/public-ingress
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill public-ingress-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the hassle of manually exposing a local Vellum gateway to the public internet so external services can reach it reliably.

Core Features & Use Cases

  • Public tunnel creation: Installs and starts ngrok to generate a publicly reachable HTTPS URL for inbound webhooks and OAuth callbacks.
  • Safety guard for managed environments: Detects when platform-managed callback routing is available and stops to avoid conflicting routes.
  • Persistent configuration: Saves the discovered ngrok public URL as ingress.publicBaseUrl and enables ingress for the assistant.

Use case: You want to receive a Telegram webhook and complete Google/Slack OAuth redirects while running a local assistant; this Skill creates the tunnel, discovers the public URL, and stores it for use by your integrations.

Quick Start

Tell the assistant: "Run the public-ingress skill to set up ngrok and persist my public ingress URL for local webhook and OAuth callbacks."

Frequently Asked Questions about public-ingress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I expose my local assistant to public webhooks using ngrok?

Setting up ngrok public ingress exposes your local Vellum gateway to the internet via an HTTPS tunnel. This allows external services to reach local webhook endpoints and OAuth redirect callback URLs reliably.

How do I get a public URL for local OAuth callbacks with Telegram and Google?

To get a public URL for local OAuth callbacks, the skill starts an ngrok tunnel and extracts the public HTTPS URL from the local ngrok API. It then persists this URL as ingress.publicBaseUrl for Telegram and Google or Slack integrations.

Do I need to manually configure ngrok authentication to expose a local gateway?

You do not need to manually handle ngrok authentication entirely yourself. The skill configures ngrok authentication, starts and verifies the tunnel, and automatically extracts the public URL to enable ingress for your local gateway.

Can I use ngrok public ingress if my platform already manages callback routing?

You should not use ngrok public ingress if platform-managed callback routing is available. The skill includes a safety guard that detects managed environments and stops to avoid conflicting routes.

How does ngrok tunnel configuration persist the public base URL for a local assistant?

Ngrok tunnel configuration persists the public base URL by extracting the generated HTTPS address from the local ngrok API and saving it as ingress.publicBaseUrl. This enables ingress and ensures integrations use the correct public endpoint.