Pi

Drop the Dial skill into your Pi config so the terminal agent learns how to drive the dial CLI on demand. Once installed, Pi can send messages, place calls, and wait for events without you re-explaining the surface.

Install

First, get the dial CLI on your PATH:

$
curl -fsSL https://getdial.ai/install | bash

Then drop the Pi-specific Dial skill into your config:

$
dial onboard --code <code> --agent pi

onboard finishes verification first, then copies the Dial skill into Pi’s standard config directory. Re-run the command anytime (after a CLI upgrade, for example) to overwrite the skill in place — the verification step is a no-op once you’re onboarded.

What gets installed

A single markdown skill describing the dial CLI — its commands, flags, and conventions, mirroring the CLI reference. Pi loads the skill when a Dial-related task comes up; nothing else is touched.

Use it

Once installed, just ask in plain language:

Send an SMS to +14155550123 with the body “running late, ETA 10 min”.

Pi picks up the skill, picks the right dial command, and runs it. See Using Dial from an agent for more examples.

Inbound event handling (Suggestion)

You can also wake Pi automatically when a Dial event arrives by wiring a CLI command target: for each inbound event, the listen daemon spawns a handler that delivers a fresh prompt to Pi’s print mode.

First install the listen daemon:

$
dial listen install

1. Write a handler

$
#!/usr/bin/env bash
$
# /usr/local/bin/handle-dial-event-pi
$
event="$1"
$
$
type=$(jq -r '.type'        <<<"$event")
$
from=$(jq -r '.from // ""'  <<<"$event")
$
body=$(jq -r '.body // ""'  <<<"$event")
$
$
prompt=$(cat <<EOF
>
A Dial event just arrived. Decide what to do and act on it.
>
>
  type: $type
>
  from: $from
>
  body: $body
>
>
raw event JSON:
>
$event
>
EOF
>
)
$
$
# Detach a fresh Pi run and return right away.
$
nohup pi -p "$prompt" </dev/null >>~/.dial/pi.log 2>&1 &
$
disown
$
exit 0

pi -p is Pi’s print mode — answer a single prompt and exit. For embedded use cases, Pi also exposes an RPC mode over stdin/stdout; see the Pi docs for the JSON protocol.

2. Register

$
chmod +x /usr/local/bin/handle-dial-event-pi
$
dial local-target add cmd /usr/local/bin/handle-dial-event-pi

The nohup … & disown pattern keeps Pi running after the handler exits, so a multi-minute agent run never collides with the daemon’s per-attempt --timeout. See CLI command target for the full reference, delivery semantics, and the once-retry behavior.