Skip to Content
sedge

Commands

Commands for the terminal and the TUI, and the tools the agents use.

Command line

CommandWhat it does
sedge [message]Open the TUI; starts the daemon in the background if needed.
sedge -p "<prompt>"Print one reply and exit.
sedge dash [tab] [agent]The dashboard, full screen: agents, inbox, runs, outbox, timers, memory, logs.
sedge startStart the daemon. --service also starts it at login.
sedge stopStop the daemon now, and remove the login service; a run cut short resumes at next start.
sedge updateUpdate now. --check only says whether there's a new version.
sedge install <package>Install channels and signals: an official name (telegram, …), an npm name, or a folder.
sedge uninstall <package>Remove a package you installed. Disconnect what uses it first.
sedge uninstallRemove sedge; asks first (--yes doesn't). --keep-data keeps your data, not the binary.
sedge pi <command>pi's own commands: install, remove, list, config, mcp, …
sedge --version, --help

The TUI and -p also take the agent's options (--model, --continue, --resume, --thinking, …); sedge pi --help lists them.

In the TUI

CommandWhat it does
/sedgeThe dashboard: agents, inbox, runs, outbox, timers, memory, logs (Agents).
/sedge <tab> [agent]Open the dashboard on a tab (inbox, outbox, …), or on one agent's share.
/sedge statusThe daemon's version and what it's doing.
/sedge bg <task>Hand a task to the daemon; a note appears when it's done.
/sedge tell <agent> <task>The same, for one agent.
/sedge stopStop the daemon now; a run cut short resumes at the next start.

All of pi's commands work too (/login, /model, /mcp, …).

Tools the TUI's agent has

Ask in your own words; these are what it uses.

ToolWhat it does
channelsWhat sedge talks to you on, and the channel kinds installed.
signalsWhat wakes sedge, what it does for each, and the signal kinds installed.
find_packagesSearch npm for channels and signals, official and community (sedge-kit).
installInstall a package of channels and signals (you confirm).
uninstallRemove a package; what it provides must be disconnected first (you confirm).
connectConnect a channel or signal; asks for secrets in a hidden field.
inviteA new one-time pairing link for a channel.
update_signalChange a signal's instruction, filters, windows or triage (you confirm).
disconnectStop one and delete its settings and secrets (you confirm).
create_signalRegister a signal or channel module it wrote (you review it first).
agentsThe daemon's agents, what each handles, and how each is doing.
create_agentCreate or change an agent: its purpose and what it handles (you confirm).
remove_agentRemove an agent (you confirm).
tell_agentHand an agent a task and wait for its answer.
inboxWhat woke which agent, from where, and how it went.
outboxWhat the agents sent you, and whether it arrived.
timersThe follow-ups and schedules the agents set.
stateThe named values (mode = away), who set them and when.
modelsThe models the daemon, each agent and each channel or signal use.
set_modelSet one of those, with a thinking level if you like (you confirm).

Tools the daemon's agent has

ToolWhat it does
send_messageThe only way to reach you: text, buttons (choices), files.
tellMessage another agent; its answer comes back as an event.
subagentStart a helper on one task; its answer comes back as an event.
get_state, set_stateRead and set named values.
set_timerA follow-up (in, at) or a schedule (cron).
list_timers, cancel_timerSee and cancel this conversation's timers.
recallSearch all past conversations.
tool_searchFind tools of MCP servers.
read, write, edit, bashFiles and the shell (see Security).
ls, find, grepLook around without the shell.

On Windows the shell tool is powershell instead of bash. A subagent has all of these except send_message, tell, subagent, set_state and the timer tools.

On this page