Book, view, and manage your Jane (janeapp.com) appointments across every clinic from one terminal — with a unified agenda, next-opening finder, and availability watch the patient portal can't do.
Jane is the booking platform behind thousands of physio, massage, chiro, and wellness clinics, but each clinic is a separate subdomain with its own login and no public API. This CLI holds a profile per clinic, imports the session from a browser where you're already logged in (Jane gates password login behind reCAPTCHA), and unifies booking, viewing, and managing appointments across all of them. agenda merges every booking into one view; next-opening pages past Jane's 7-day availability cap to find the soonest slot.
Learn more at Jane App.
Created by @omarshahine (Omar Shahine).
Authentication
Each Jane clinic is its own subdomain with a separate patient account, and Jane gates username/password login behind reCAPTCHA. So the CLI imports the _front_desk_session cookie from a browser where you're already logged in: register a clinic (clinic add <name> --url=https://<clinic>.janeapp.com), log in to it once in your browser, then run auth login --clinic <name> --chrome (or --cookies-file <file>). Repeat per clinic; read commands accept --all-clinics.
Quick Start
# Register a clinic; each keeps its own subdomain and session.
janeapp-pp-cli clinic add embophysio --url=https://embophysio.janeapp.com
# Log in to the clinic in Chrome first, then import that session (Jane blocks CLI password login via reCAPTCHA).
janeapp-pp-cli auth login --clinic embophysio --chrome
# View your upcoming appointments at that clinic.
janeapp-pp-cli appointments upcoming --clinic embophysio
# List practitioners so you have IDs for availability and booking.
janeapp-pp-cli staff --clinic embophysio
# Find the soonest bookable slot, paging past the 7-day window.
janeapp-pp-cli next-opening --clinic embophysio --treatment 1 --staff 1
# Every appointment across every logged-in clinic in one view.
janeapp-pp-cli agenda
Unique Features
These capabilities aren't available in any other tool for this API.
Cross-clinic
-
agenda — See every appointment across every Jane clinic you use in one chronological view.
One call answers 'what do I have coming up anywhere' instead of logging into each clinic portal separately.
janeapp-pp-cli agenda --agent
-
conflict-check — Before booking, warn if a candidate slot collides with an existing appointment at another clinic.
Prevents double-booking yourself across different clinics.
janeapp-pp-cli conflict-check --at 2026-07-15T09:00:00 --duration 60
Availability intelligence
-
next-opening — Find the soonest available slot for a practitioner + treatment, paging past Jane's 7-day availability cap.
Answers 'when is the earliest I can get in' without clicking week-by-week through the portal.
janeapp-pp-cli next-opening --clinic embophysio --treatment 1 --staff 1
-
watch — Poll availability and alert when an earlier slot than a target opens up.
Catches cancellations that free up an earlier appointment.
janeapp-pp-cli watch --clinic embophysio --treatment 1 --staff 1 --before 2026-08-01
Recipes
Unified agenda across clinics
janeapp-pp-cli agenda --agent --select clinic,date,start_at,practitioner,treatment
Every upcoming appointment from every logged-in clinic, narrowed to the fields an agent needs.
Earliest slot with a specific PT
janeapp-pp-cli next-opening --clinic embophysio --treatment 1 --staff 1
Stitches 7-day windows until it finds the first available opening.
Export appointments to a calendar file
janeapp-pp-cli calendar --all-clinics --out ~/jane.ics
Generates an ICS from your appointments across every clinic; import into Apple/Google Calendar or subscribe live with 'calendar --url'.
Book a slot (dry-run first)
janeapp-pp-cli book --clinic embophysio --treatment 1 --staff 1 --location 1 --at 2026-07-15T09:00:00
Shows the reserve/confirm request without writing; add --confirm to actually book.
Usage
Run janeapp-pp-cli --help for the full command reference and flag list.
Paths & environment variables
This CLI separates local files into four path kinds:
| Kind | Contents |
|---|
config | User-editable settings such as config.toml and saved profiles |
data | Durable local data: credentials.toml, data.db, cookies, browser-session proof files, and other auth sidecars |
state | Runtime state such as persisted queries, jobs, and teach.log |
cache | Regenerable HTTP/cache files |
Each kind resolves independently. The ladder is:
- Per-kind env var:
JANEAPP_CONFIG_DIR, JANEAPP_DATA_DIR, JANEAPP_STATE_DIR, or JANEAPP_CACHE_DIR
--home <dir> for this invocationJANEAPP_HOME for a flat relocated root- XDG env vars:
XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME
- Platform defaults matching existing installs
For containers and agent sandboxes, prefer a single relocated root:
export JANEAPP_HOME=/srv/janeapp
janeapp-pp-cli doctor
Under JANEAPP_HOME=/srv/janeapp, the four dirs resolve to /srv/janeapp/config, /srv/janeapp/data, /srv/janeapp/state, and /srv/janeapp/cache.
MCP servers do not receive CLI flags from the host. Put relocation in the host env block:
{
"mcpServers": {
"janeapp": {
"command": "janeapp-pp-mcp",
"env": {
"JANEAPP_HOME": "/srv/janeapp"
}
}
}
}
Precedence matters in fleets: an ambient per-kind variable such as JANEAPP_DATA_DIR overrides an explicit --home for that kind. Use JANEAPP_HOME or the per-kind variables for durable fleet relocation; treat --home as the weaker per-invocation lever.
Relocation is one-way. Unsetting JANEAPP_HOME does not move files back to platform defaults, and doctor cannot find credentials left under a former root. Move the files manually before unsetting relocation variables.
Existing installs keep working because the platform-default rung matches the legacy layout. On the first auth write, stored secrets leave config.toml and are consolidated into credentials.toml under the data directory. Run janeapp-pp-cli doctor --fail-on warn to check path and credential-location warnings in automation.
Commands
appointments
Your own appointments at the clinic (requires a logged-in session).
janeapp-pp-cli appointments upcoming / janeapp-pp-cli appointments past - View your upcoming or past appointments (add --all-clinics to merge every logged-in clinic). Requires a logged-in session.
disciplines
Disciplines (categories of care) offered by the clinic, e.g. Physical Therapy.
janeapp-pp-cli disciplines - List disciplines (service categories) with descriptions.
locations
Clinic locations (address, phone, booking URL) for the active profile's Jane instance.
janeapp-pp-cli locations - List clinic locations with address, contact info, and booking URL.
openings
Live availability (openings) for a practitioner + treatment at a location.
janeapp-pp-cli openings - List available appointment openings for a staff member + treatment at a location over a date window. Jane caps num_days at 1..7; the CLI's next-opening/watch commands page across multiple windows automatically.
staff
Practitioners (staff members) and the treatments they offer.
janeapp-pp-cli staff - List practitioners, their bookable treatment IDs, and online-booking availability.
treatments
Bookable treatments/services with price, duration, and online-booking eligibility.
janeapp-pp-cli treatments - List treatments (services) with price, duration, discipline, and whether they can be booked online.
Output Formats
# Human-readable table (default in terminal, JSON when piped)
janeapp-pp-cli appointments
# JSON for scripting and agents
janeapp-pp-cli appointments --json
# Filter to specific fields
janeapp-pp-cli appointments --json --select id,name,status
# Dry run — show the request without sending
janeapp-pp-cli appointments --dry-run
# Agent mode — JSON + compact + no prompts in one flag
janeapp-pp-cli appointments --agent
Agent Usage
This CLI is designed for AI agent consumption:
- Non-interactive - never prompts, every input is a flag
- Pipeable -
--json output to stdout, errors to stderr
- Filterable -
--select id,name returns only fields you need
- Previewable -
--dry-run shows the request without sending
- Read-only by default - this CLI does not create, update, delete, publish, send, or mutate remote resources
- Offline-friendly - sync/search commands can use the local SQLite store when available
- Agent-safe by default - no colors or formatting unless
--human-friendly is set
Exit codes: 0 success, 2 usage error, 3 not found, 4 auth error, 5 API error, 7 rate limited, 10 config error.
Freshness
This CLI owns bounded freshness for registered store-backed read command paths. In --data-source auto mode, covered commands check the local SQLite store before serving results; stale or missing resources trigger a bounded refresh, and refresh failures fall back to the existing local data with a warning. --data-source local never refreshes, and --data-source live reads the API without mutating the local store.
Set JANEAPP_NO_AUTO_REFRESH=1 to disable the pre-read freshness hook while preserving the selected data source.
Covered command paths:
janeapp-pp-cli disciplinesjaneapp-pp-cli disciplines getjaneapp-pp-cli disciplines listjaneapp-pp-cli disciplines searchjaneapp-pp-cli locationsjaneapp-pp-cli locations getjaneapp-pp-cli locations listjaneapp-pp-cli locations searchjaneapp-pp-cli openingsjaneapp-pp-cli openings getjaneapp-pp-cli openings listjaneapp-pp-cli openings searchjaneapp-pp-cli staffjaneapp-pp-cli staff getjaneapp-pp-cli staff listjaneapp-pp-cli staff searchjaneapp-pp-cli treatmentsjaneapp-pp-cli treatments getjaneapp-pp-cli treatments listjaneapp-pp-cli treatments search
JSON outputs that use the generated provenance envelope include freshness metadata at meta.freshness. This metadata describes the freshness decision for the covered command path; it does not claim full historical backfill or API-specific enrichment.
Health Check
janeapp-pp-cli doctor
Verifies configuration, credentials, and connectivity to the API.
Configuration
Run janeapp-pp-cli doctor to see the resolved config, data, state, and cache directories. The platform-default config path is ~/.config/janeapp-pp-cli/config.toml; --home, JANEAPP_HOME, and per-kind env vars can relocate it.
Static request headers can be configured under headers; per-command header overrides take precedence.
Troubleshooting
Authentication errors (exit code 4)
- Run
janeapp-pp-cli doctor to check credentials
Not found errors (exit code 3)
- Check the resource ID is correct
- Run the
list command to see available items
API-specific
- auth login says reCAPTCHA required / lands on /auth/failure — Jane blocks CLI password login. Log in to the clinic in your browser, then import with 'auth login --clinic --chrome'.
- appointments return 401 — Your imported session expired — log in again in the browser and re-run 'auth login --clinic --chrome'.
- openings returns 'Number of days must be an integer between 1 and 7' — Use num-days 1..7; for longer horizons use next-opening/watch which page automatically.
Known Gaps
Jane exposes no public patient API, so this CLI is built against its live web
endpoints. Coverage is verified to different depths:
- Verified live (public, unauthenticated):
locations, disciplines,
treatments, staff, openings, and next-opening were exercised against
real Jane clinics.
- Auth is browser-session import, not password. Jane gates username/password
login behind reCAPTCHA, so
auth login imports the _front_desk_session cookie
from a browser where you're already logged in (--chrome / --cookies-file).
A --username/--password path exists but Jane rejects it with a reCAPTCHA
error; the CLI detects this and points you to the cookie path.
- Verified live (authenticated):
auth login --chrome, appointments
(upcoming/past), agenda, openings/next-opening (future dates), book, and
calendar were all confirmed against a real logged-in account.
book, cancel, and reschedule are verified live against a real account:
book runs Jane's reserve → confirm flow (POST /api/v2/reservations then
POST /api/v2/appointments/{id}/book).cancel is DELETE /api/v2/appointments/{id} (the patient endpoint; the
/cancel suffix is the staff API).reschedule books the new slot first, then cancels the old with a fresh CSRF
token (Jane rotates it after each mutation) — so a failed new booking never
loses your original appointment.
All three are dry-run by default; add --confirm to submit.
- Cancelled appointments are excluded from
upcoming/agenda but shown in
past and the ICS feed (with STATUS:CANCELLED).
- Availability uses
date, not start_date. Jane's /api/v2/openings keys the
window on date; passing start_date is silently ignored (it returns only the
current week). The CLI sends date — a fix over the initial spec guess.
calendar generates a .ics from your appointments (--out) and prints
Jane's native live subscribe URL (--url) for auto-syncing in a calendar app.