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.
$ 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¶
-
Four backends, one engine
Microsoft Graph, Google, Apple iCloud, and any CalDAV host. Switch providers, change nothing.
-
Real workflows
Approval chains, timeouts, day-of-week and attendee guards, delays, and branching, written as JSON you can read and share.
-
Where you already work
Drive it from the CLI, Claude over MCP, or Slack with Approve and Decline buttons.
-
Tell the team
Fan out to the team as optional attendees, and announce the outcome to a Slack channel or 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.