vamoose

Calendar workflows, minus the tedium.

The moose does the paperwork. You go to the beach. Four calendar backends behind one workflow engine, driven from your terminal, Claude, or Slack.

Get started View on GitHub

vamoose

$ vamoose off next week --subject "Out: beach week" Hold created and sent to boss@work.com for approval. Hold id: AAMk… $ vamoose check Approved by boss@work.com. $ vamoose promote Added 4 team members as optional from the directory. Everyone notified.

brew install dcadolph/tap/vamoose

How it works

1RequestBlock the dates shown free, so no calendar is touched, and invite your manager.

2ApproveYour manager accepts the invite. That acceptance is the approval, no extra tool.

3NotifyThe team is added as optional attendees, so everyone sees you are out.

Why vamoose

• Any calendar

  ---

  Microsoft Graph, Google, Apple iCloud, and any CalDAV host, behind one interface. Switch providers, change nothing.

• A real workflow engine

  ---

  Branch on outcomes, gate on approval, guard by day or headcount. A state machine in JSON, not a dumb calendar rule.

• Approvals that mean it

  ---

  Manager, then director, in sequence. Timeouts that act on silence, decline paths, and the accept-the-invite signal, no approval product to buy.

• Acts on time

  ---

  Wait steps pause a run; schedules rerun a whole workflow weekly. It moves on its own, in the background.

• Drivable by AI

  ---

  Over MCP, an agent discovers, previews, runs, schedules, and even authors workflows. The calendar-workflow layer for Claude.

• Tells everyone

  ---

  Fan out to the team as optional attendees, and announce the outcome to a Slack channel or by email.

Start here

• Quickstart — zero to your first approved hold in a few minutes.
• Concepts — how holds, approval, and workflows fit together.
• Commands — every command, flag, and environment variable.
• Workflows — design your own, with branching, delays, and guards.