Callout

Keep track of all your meeting-related information in one place.

Callout is a local-first app for meeting facilitators to organize, search, and access meeting resources when leading meetings.

You can quickly access the docs, links, and notes you need to present and share with meeting attendees, without having to keep multiple tabs and windows open at once. You organize meeting resources into workspaces before meetings and even during meetings. Resources can be shared across workspaces or pinned to the top for easy access.

No more struggling to find resources while you’re facilitating.

Callout is Windows-only today. This is still a work-in-progress, so stay tuned for updates.

How it works

1. Make a workspace for a meeting (e.g., Product Review, Weekly Standup).
2. Add relevant resources (URLs, files, or notes) that you need to present or that your meeting attendees may ask for, OR tell your agent to add these.
3. Use the notes section in the agenda or keep track of any details mentioned.
4. Next time you have the same meetings, update the workspace resources as needed.
5. (Optional) Add shared resources you may need across multiple meetings.

Callout is agent-native by design, so you can tell your agent (e.g., Claude Code, Codex, Gemini) to manage workspaces and meeting resources for you. If your agent has access to all the relevant details, it can directly use the CLI to set up the workspace for your meeting, so you’re ready to present and lead the meeting.

You can tell your agents to

• Set up a workspace: "Set up a 'Customer Onboarding' workspace with our welcome doc, the Jira board, and the metrics dashboard, and pin the welcome doc."
• Add resources: "Add our standard pricing blurb in Shared Resources so I can paste it in any customer call."
• Customize workspaces: "I’m meeting with a new enterprise client, add relevant resources to my Customer Onboarding workspace."
• Find resources: “Find that customer note I made about referral codes”
• Back up: "Export all my Callout data to a file on my Desktop."

Quickstart

Requires Node 22+ and pnpm 10. From a clone of this repo:

pnpm install
pnpm build

Run the desktop app — build the Windows installer and run it:

pnpm --dir apps/desktop run package        # output: apps/desktop/release/Callout Setup <version>.exe

Launch the installer, then create your first workspace. Full walkthrough: docs/getting-started.md.

Use the CLI (for agents and scripts) — link the callout command globally:

pnpm --dir packages/cli link --global      # then: callout workspace list
# (or skip the link and run: node packages/cli/dist/cli.js <command…>)

The app and CLI data are both stored in a shared database %APPDATA%\Callout\callout.db, so any change made by your agent is synced with changes you make in the app.

Features

• Workspaces: Group three types of resources per meeting: URLs, files, or text snippets.
• Shared Resources: A reserved workspace for the links and blurbs you reach for across many meetings. You can add these to any workspace as necessary.
• Search: Lookup workspaces and resources.
• Open All: Opens every resource in a workspace (if you want), so you’re ready when a meeting begins.
• Workspace Notes: Add meeting-specific notes you may need to reference.
• Meeting Mode: A compact, always-on-top panel for live calls. Pinned resources show up as cards (drag to arrange) along with your workspace note.
• Agent-native CLI: Every capability above is also a callout CLI command, so an agent can do anything you can, even with the app closed.

Security note

The callout CLI lets any local process open files and URLs with your default applications and read/modify your Callout data, but treat it with the same care as shell access. The settings toggle "Confirm before opening file resources triggered externally" makes the CLI require an interactive confirmation (or an explicit --yes) before opening file resources.

Agent use

Callout is designed to be driven by a local coding agent through the callout CLI. Point the agent at AGENTS.md, so it can understand how to use the app.

• Structured output — every read command takes --json, so the agent gets machine output instead of scraped tables.
• Name or id — resolve a workspace or resource by its title (callout open "Q3 Roadmap"), not just an id; ambiguous names return the candidate list.
• Stable exit codes — 0 success · 2 validation/ambiguous · 3 not found · 1 other; errors are one-line JSON on stderr.
• Works with the app closed — the CLI reads and writes the same SQLite file as the app, so an agent can set up a meeting overnight; it appears in the app on next launch.

callout workspace create "Design Crit" -d "Thursdays 14:00"
callout resource add --title "Figma file" --url https://figma.com/file/xyz --pin \
  --workspace "Design Crit"
callout workspace get "Design Crit" --json     # full summary as JSON

Documentation

Doc	What's in it
docs/getting-started.md	Using the app
AGENTS.md	CLI reference for agents
docs/ARCHITECTURE.md	Package boundaries, IPC, concurrency, testing
docs/DESIGN.md	Design system

License

MIT — see LICENSE.