CLI for Jane (janeapp.com) patient online booking. Log in to any Jane clinic
with your patient username and password, browse practitioners, treatments, and
live availability, view your upcoming and past appointments, and book, reschedule,
or cancel — across every clinic you use, from one tool. Jane is multi-tenant: each
clinic is its own subdomain (e.g. embophysio.janeapp.com), so each profile stores
its own base URL and session.
Learn more at Janeapp.
Created by @omarshahine (Omar Shahine).
Quick Start
1. Install
See Install above.
2. Authenticate
Jane is multi-tenant: each clinic is a separate janeapp.com subdomain with its own patient session, and auth login saves the session to the currently selected clinic. Register and select your clinic first:
janeapp-pp-cli clinic add myclinic # registers myclinic.janeapp.com
janeapp-pp-cli clinic use myclinic
This CLI uses your browser session for authentication. Log in to .janeapp.com in Chrome, then:
janeapp-pp-cli auth login --chrome
Or import an existing browser capture:
janeapp-pp-cli auth login --cookies-file storage-state.json
--cookies-file accepts Playwright storage-state JSON or a raw Cookie: header text file. The Chrome path requires a cookie extraction tool. Install one:
pip install pycookiecheat # Python (recommended)
brew install barnardb/cookies/cookies # Homebrew
When your session expires, run auth login --chrome again.
3. Verify Setup
janeapp-pp-cli doctor
This checks your configuration and credentials.
4. Try Your First Command
janeapp-pp-cli appointments
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 - List your upcoming and past appointments for the active profile.
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.
Self-learning loop
This CLI caches per-question discovery so repeat queries skip the walk and structurally similar queries get answered via entity substitution. The loop also self-captures: every invocation is journaled locally, and failed-flag corrections plus fresh teaches surface as candidates on the next recall for confirm/reject judgment. Agents call recall before discovery and fire teach & after answering. See the ## Automatic learning section in SKILL.md for the full protocol.
janeapp-pp-cli recall <query> - Look up cached resources for a query before running discoveryjaneapp-pp-cli teach - Record a query -> resource mapping (silent on success, safe to background with &)janeapp-pp-cli learnings list - Inspect taught rowsjaneapp-pp-cli learnings forget <query> - Undo a teachjaneapp-pp-cli learnings candidates - List auto-captured candidates awaiting confirm/rejectjaneapp-pp-cli learnings stats - Local loop metrics: recall hit rate, teach-to-reuse, playbook resolution, candidate countsjaneapp-pp-cli teach-pattern - Install a query/resource template up frontjaneapp-pp-cli teach-lookup - Add an entity mapping (e.g. country code, team alias) for pattern substitution
Pass --no-learn or set JANEAPP_NO_LEARN=true to disable the loop for deterministic flows.
The local store's schema version stamp is one-way: once this version of janeapp-pp-cli opens the database, older binaries refuse it with a version error — upgrade the binary rather than downgrading.
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 appointmentsjaneapp-pp-cli appointments getjaneapp-pp-cli appointments listjaneapp-pp-cli appointments searchjaneapp-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
Generated by CLI Printing Press