Pilot in Command

Projects

Chats

…

Pilot in Command

Choose an agent to begin.

Import agents from a team folder

Enter to send · Shift+Enter for a new line

New agent

? Choose picture

Name Role

Default model Privacy Voice (voice id, voice name or reference .wav; blank = default)

One-line summary (what this agent is good for; shown to agents that direct it) May write to the shared team memory

Authority — this agent may hand tasks to:

Tools this agent may use

System prompt

New project

Name Description Default model Project instructions

Settings

Add model provider

Provider id Type

Base URL

Runs Models to list (comma separated; empty = ask the provider)

API key (stored owner-only in secrets.toml; leave blank to keep the current one) Enabled

Add MCP server

Server id Type

Description

URL Bearer token (stored owner-only; leave blank to keep)

Command Arguments (one per line) Environment (KEY=value per line; use secret:NAME to pull from secrets.toml)

Enabled

Add email account

Account id Display name

Email address Login user (usually the address)

IMAP host IMAP port

SMTP host SMTP port (465 TLS, 587 STARTTLS)

Password or app password (stored owner-only; blank keeps the current one) Enabled

Gmail: turn on 2-Step Verification, then create an App Password in your Google account and paste it here. Workspace accounts that block app passwords need the Google sign-in route, which is next on the list.

New trigger

Trigger id Kind

Agent Model

Description Schedule (minute hour day month weekday; e.g. 0 7 * * 1-5 = 7:00 on weekdays) Folder to watch Webhook token (blank = generate one) Receive through the rendezvous host (for services that cannot reach this node directly) Email account id Prompt (placeholders: {{file}} {{filename}} {{body}} {{from}} {{subject}} {{now}}) Enabled

Model

Engine

IdName

Command Arguments, one per line

Working folder (optional)Health URL (optional)

Environment, KEY=value per line (optional) Notes Start with the node

Import agents from a team folder

Team folder

Each NAME - Role folder with a SYSP file becomes an agent: prompt from the SYSP, memories from the *_Memories file, portrait from an avatar image if present. The team folder is added as a file-tool root and each Inbox gets a watcher.

Default model for new agents create Inbox watchers

Save this chat as a skill

The agent distils what was done here into a reusable procedure (a SKILL.md) with the inputs as variables, so next time it asks for the values and runs the steps.

Skill nameWho can use it

Notes for the distiller (optional)

Welcome. Two steps and you are flying.

1. Where should your agents think?

A cloud model with my API key
Anthropic, OpenAI, xAI, DeepSeek, OpenRouter. Pay the provider per use. On this machine
Ollama or llama.cpp. Private, free to run, needs a model file.

ProviderAPI key

Checking for Ollama…

2. Your first agent

NameRole

Start from What this agent is for (becomes the prompt; edit any time)

Access key

This node requires an access key. Paste one created under Settings → Access on the node.

Node address (hosted copy only) Key

You are in command. The AI flies.

Pilot in Command · by Airborn Tech

Every install is a full node. Your agents, chats and memory live on your own machine. Cloud models see only what you send them; local models never leave the building.