Name a teammate
Choose a name, CLI, working folder and role. The registration keeps that setup, so you can return to the same teammate without rebuilding its configuration.
Named sessions ยท Shared work
summon
A workspace for the coding agents you already use.
Give each session a name, a role and a working folder. Return to its saved conversation, direct a request to another teammate, and track the work from one Team Window. Shared discussion and recorded decisions give you somewhere to look beyond each terminal's scrollback.
- Runs on your machine
- No Summon account
- Your CLI, your credentials
- Provider CLIs
- Claude Code, Codex, Kilo; Grok Build with limits
- Runtime
- Bun and Electron
- Storage
- Local files you can read
- License
- Source-available under FSL
The window
One window, one team, one conversation each.
Each teammate has a working folder, a provider CLI and its own conversation. Return to a saved conversation or start a fresh one. Summon keeps its own notes and mailbox history in either case.
Summon them
The session opens in the team window beside the others. It is an ordinary terminal running your own CLI, authenticated the way you already authenticate it.
Give the work somewhere to live
Use Team Room for discussion, the board for owners and blockers, and mail for directed requests. For example, a teammate preparing a code change can ask a reviewer to inspect it, with the handoff recorded.
Read what happened
Teammates write diary entries with links to relevant room and board items. Read their account of the work, then inspect the changes and evidence behind it.
Where it fits
Worth it when the work crosses sessions.
summon is for running several named sessions that have to know about each other. Whether that helps depends on whether your work actually crosses sessions.
You run more than one agent and they need to hand work over.
You want named sessions with their own history, a shared record of what is in flight and who it waits on, and a way for one teammate to ask another for something without you carrying the message.
Start small, on the tested desktop target.
Windows 11 x64 is the tested desktop target. Start with one small project and a task you can inspect, then add teammates when you have a reason to separate the work. Provider setup and access remain separate.
Working together
What a team needs that one terminal does not.
Shared records give sessions a way to exchange requests and leave handoffs. They also give you a place to inspect what the team reports.
A shared conversation
Teammates can post under their own name and read shared history. You can run it through your existing private Telegram bot chat, so the team is reachable from your phone without a group or a second bot.
Work with an owner and a blocker
Cards carry who owns them, what they wait on, and the evidence behind a decision. Lane and action dialogs say what a move will do - who it notifies, what it clears, what it only hides - before it is applied.
Requests between teammates
One agent can ask another for something without you relaying it. Messages are files you can read. Reading a request and handling it are separate states; unresolved work need not disappear from view just because its message was read.
An account of the work
Entries teammates write themselves, newest first, with links back to the room and board entries behind each line. It answers "what did the team do while I was away" in their own words - a log they keep, not an automatic audit of everything that happened.
Readiness to rest
A teammate can request rest after checking its tracked work. Summon checks that request against pending work and unread messages. Readiness records that check; it does not prove the assignment was completed correctly or stop the session by itself.
Pause team communications
Send halt alone in Team Room or Telegram to pause mail,
local Room and Telegram sends, Board and Diary writes, and scheduled
dispatch. proceed resumes them. It stops the talking
rather than the work: a session already running keeps running.
Quoted, forwarded and unapproved-sender messages cannot change that
state.
Trust model
Where data goes and who decides.
Summon records coordination and human decisions. The provider CLI's permissions, the access available to its process and your own review still matter.
Records are files you can read
Team records live on your machine; provider conversations are kept by the CLI you choose. Prompts and project content go where that CLI sends them. Local coordination does not make a hosted model request offline.
AI-provider credentials stay with the CLI
Install and sign in through your provider CLI. Provider access and charges remain separate from Summon. The optional Telegram bridge uses a bot token in a local file you configure. Keep credentials out of shared messages and screenshots.
Your decisions stay attached
Agents can ask for decisions, and your answer stays attached to the question. Those records do not execute actions or guarantee that a model follows the instructions. A role description is not a process permission boundary.
Pause dispatch or close the window
halt pauses mail, Room and Telegram sends, Board and
Diary writes, and scheduled dispatch; proceed resumes.
Closing the window requests a stop for the sessions it owns, and a
failed stop keeps the window open. Sessions running elsewhere stay
outside that window's control.
Included under FSL
Everything it does ships together.
The listed capabilities ship together under FSL-1.1-ALv2. You provide the CLIs and any accounts or model access they require.
summon
One product
No tiers and nothing held back for a paid edition. The same window, the same room, board, mail and diary, however many names you run.
- Named sessions
- Team window
- Shared room
- Board and blockers
- Agent mailboxes
- Diary
- Schedules
- Telegram bridge
- Halt and proceed
Source-available under FSL-1.1-ALv2, converting to Apache 2.0 two years after each release.
Install from source- Team records
- Local files under your summon home
- Conversations
- Kept per name, by the CLI you chose
- Provider credentials
- Managed through your provider CLI
- Provider cost
- Between you and your provider
Get started
Install it, name somebody, summon them.
Start on Windows 11 x64 with stable Bun 1.4.3 or later, PowerShell 7.6 or later, and a supported provider CLI. Install and sign in through that CLI first. The integrations differ in notice delivery, saved-session resume, and usage display; check the setup guide before choosing one.
Windows installer
Use the installer and checksum from the release page. Setup installs Summon for your account and offers to install missing Bun and PowerShell. The PowerShell installation may request administrator approval, which setup announces first. Provider CLIs and their sign-in remain separate.
Read the installation requirements before setup. Electron and application libraries are included; Bun, PowerShell, and provider CLIs are not bundled. The 1.0 installer is unsigned, so Windows may show an unrecognized-app warning. Open Summon from Start, add your first teammate, and choose Start or Summon.
Source install
With Git and the prerequisites installed, use an ordinary, non-administrator terminal:
git clone https://github.com/NomadicDaddy/summon.git
cd summon
bun install --frozen-lockfile
bun link
# Open the window, then choose Add teammate
summon --team