pp-jimmy-johns

name pp-jimmy-johns description Order Jimmy John's from the terminal — Freaky Fast Rewards stacking, half-order builder, and one-shot reorder. author Omar Shahine license Apache-2.0 argument-hint <command> [args] | install cli|mcp allowed-tools Read Bash metadata {"openclaw":{"requires":{"bins":"[Truncated]"},"install":["[Truncated]"]}} Jimmy Johns — Printing Press CLI Prerequisites: Install the CLI This skill drives the jimmy-johns-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first: Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows: npx -y @mvanhorn/printing-press-library install jimmy-johns --cli-only Verify: jimmy-johns-pp-cli --version Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill. If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.5 or newer). This installs into $GOPATH/bin (default $HOME/go/bin ), so add that directory to $PATH instead: go install github.com/mvanhorn/printing-press-library/library/food-and-dining/jimmy-johns/cmd/jimmy-johns-pp-cli@latest If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH . Do not proceed with skill commands until verification succeeds. CLI for the Jimmy John's ordering API. Browse stores, menus, and product modifiers; manage your cart; place orders; view rewards and saved payments. Backed by Jimmy John's proprietary API at www.jimmyjohns.com/api and authenticated via cookies imported from a logged-in Chrome session (PerimeterX clearance + JJ session cookies). HTTP Transport This CLI uses Chrome-compatible HTTP transport for browser-facing endpoints. It does not require a resident browser process for normal API calls. Command Reference account — User account, profile, addresses, and saved payments jimmy-johns-pp-cli account current — Get the authenticated user's profile (name, email, preferences). jimmy-johns-pp-cli account delivery-addresses — List the authenticated user's saved delivery addresses. jimmy-johns-pp-cli account login — Authenticate with email + password. Sets JJ session cookies. jimmy-johns-pp-cli account saved-payments — List the authenticated user's saved payment methods. jimmy-johns-pp-cli account web-token — Refresh the web session token (called internally by the SPA). menu — Menu products, filters, and modifier options jimmy-johns-pp-cli menu product-filters — List available menu filter dimensions (categories, dietary tags, allergens). jimmy-johns-pp-cli menu product-modifiers — List modifier groups (bread, toppings, add-ons) for a specific product. jimmy-johns-pp-cli menu products — List menu products for the current store (subs, sides, drinks, cookies, catering). order — Cart and order management jimmy-johns-pp-cli order add-items — Add one or more items to the current cart in a single call. jimmy-johns-pp-cli order current — Get the current in-progress order/cart. jimmy-johns-pp-cli order upsell — Get upsell suggestions for the current cart (sides, drinks, cookies). rewards — Freaky Fast Rewards points balance and catalog jimmy-johns-pp-cli rewards catalog — List available reward redemptions for the current points balance. jimmy-johns-pp-cli rewards summary — Get the authenticated user's rewards points balance and recent activity. stores — Jimmy John's store locations and operating info jimmy-johns-pp-cli stores get-disclaimers — Get store-specific disclaimers (delivery zone caveats, hours warnings). jimmy-johns-pp-cli stores list — List stores. Accepts an address search or filter; returns stores with hours, distance, pickup/delivery flags. system — System utilities (Google Maps signing for store finder) jimmy-johns-pp-cli system — Sign a Google Maps URL for client-side use (used internally by store finder) Freshness Contract This printed CLI owns bounded freshness only for registered store-backed read command paths. In --data-source auto mode, those paths check sync_state and may run a bounded refresh before reading local data. --data-source local never refreshes. --data-source live reads the API and does not mutate the local store. Set JIMMY_JOHNS_NO_AUTO_REFRESH=1 to skip the freshness hook without changing source selection. Covered paths: jimmy-johns-pp-cli menu jimmy-johns-pp-cli menu get jimmy-johns-pp-cli menu list jimmy-johns-pp-cli menu search jimmy-johns-pp-cli stores jimmy-johns-pp-cli stores get jimmy-johns-pp-cli stores list jimmy-johns-pp-cli stores search When JSON output uses the generated provenance envelope, freshness metadata appears at meta.freshness . Treat it as current-cache freshness for the covered command path, not a guarantee of complete historical backfill or API-specific enrichment. Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: jimmy-johns-pp-cli which "<capability in your own words>" which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query. Auth Setup This CLI uses a browser session. Log in to jimmyjohns.com in Chrome, then: jimmy-johns-pp-cli auth login --chrome Or import an existing browser capture: jimmy-johns-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 ( pycookiecheat via pip, or cookies via Homebrew). Run jimmy-johns-pp-cli doctor to verify setup. Agent Mode Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes . Pipeable — JSON on stdout, errors on stderr Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs: jimmy-johns-pp-cli stores list --agent -- select id ,name,status Previewable — --dry-run shows the request without sending Offline-friendly — sync/search commands can use the local SQLite store when available Non-interactive — never prompts, every input is a flag Explicit retries — use --idempotent only when an already-existing create should count as success Response envelope Commands that read from the local store or the API wrap output in a provenance envelope: { "meta" : { "source" : "live" | "local" , "synced_at" : "..." , "reason" : "..." } , "results" : <data> } Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag ( --json , --csv , --compact , --quiet , --plain , --select ) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout. Paths and state Agents should treat the CLI's path resolver as part of the runtime contract: Use --home <dir> for one invocation, or set JIMMY_JOHNS_HOME=<dir> to relocate all four path kinds under one root. Use per-kind env vars only when a specific kind must diverge: JIMMY_JOHNS_CONFIG_DIR , JIMMY_JOHNS_DATA_DIR , JIMMY_JOHNS_STATE_DIR , JIMMY_JOHNS_CACHE_DIR . Resolution order is per-kind env var, --home , JIMMY_JOHNS_HOME , XDG ( XDG_CONFIG_HOME , XDG_DATA_HOME , XDG_STATE_HOME , XDG_CACHE_HOME ), then platform defaults. config contains settings like config.toml and profiles. data contains credentials.toml , data.db , cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log . cache contains regenerable HTTP/cache files. Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write. Run jimmy-johns-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs. For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags: { "mcpServers" : { "jimmy-johns" : { "command" : "jimmy-johns-pp-mcp" , "env" : { "JIMMY_JOHNS_HOME" : "/srv/jimmy-johns" } } } } Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use JIMMY_JOHNS_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing JIMMY_JOHNS_HOME , or doctor will not find credentials left under the former root. Automatic learning This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a flag_alias candidate, and a teach on a query family without a playbook auto-synthesizes a playbook_candidate from the session's journal. Your job is judgment only: recall first, act on surfaced candidates, teach the final answer, playbook amend when you observe a correction. You never record failures by hand. Step 1: recall before any discovery Before list/search/drill commands on a new user question, run: jimmy-johns-pp-cli recall "<user's question>" --agent The response envelope: { "query" : "..." , "normalized" : "<normalized form>" , "query_entities" : [ "..." ] , "found" : true | false , "match_score" : 0.0 , "results" : [ { "resource_id" : "..." , "resource_type" : "..." , "venue" : "..." , "confidence" : 2 , "entity_match" : "exact|partial|unknown" , "source" : "taught|preseed|pattern" , "warnings" : [ "..." ] } ] , "mismatches" : [ /* only when --debug-mismatches */ ] , "warnings" : [ /* top-level */ ] , "candidates" : [ { "id" : 12 , "class" : "flag_alias | playbook_candidate" , "summary" : "..." , "sightings" : 3 , "last_seen" : "..." , "rationale" : "..." , "next_action" : [ "<trial command>" , "jimmy-johns-pp-cli learnings confirm 12" ] } ] , "playbook" : { "query_family" : "..." , "playbook" : { "steps" : [ { "cmd" : "<command with {slot} substitution>" , "purpose" : "..." } ] , "entity_slots" : [ "$ENTITY" ] , "expected_tool_calls" : 3 } , "slots_resolved" : { "$ENTITY" : { "token" : "<live token>" , "canonical" : "<canonical>" } } , "notes" : "<workarounds + gotchas for this query family>" } , "notes" : "<duplicate surface for non-playbook callers>" } Empty-store short-circuit: if the store has no learnings, playbooks, or candidates yet (recall finds nothing and learnings list and learnings candidates are both empty), skip recall for the rest of this session instead of taxing every query; resume recall-first once something has been taught. Step 2: decision tree Read candidates , playbook , notes , results[0] , and warnings in that order: if Candidates present (warnings include "candidates_present"): -> candidates are try-then-confirm, never facts. Follow each candidate's two-step next_action verbatim: run the trial command first, then run `learnings confirm <id>` only after the trial verified the behavior. Reject a wrong candidate with `learnings reject <id>`. -> NEVER re-teach something recall surfaced as a candidate; confirm or reject that candidate instead of teaching a duplicate. -> candidates ride alongside playbooks and resource hits, not instead of them; continue with the branches below after acting on them. if Playbook present: -> READ Playbook.notes verbatim FIRST (workarounds + gotchas the CLI surface doesn't expose) -> replay Playbook.steps in order, substituting Playbook.slots_resolved entries for the entity slot tokens. If a step's slot is unresolved, fall back to discovery for that step only. -> the Playbook's expected_tool_calls is a budget; if you find yourself running materially more, record the divergence via `jimmy-johns-pp-cli playbook amend` at end-of-session. elif Notes present (no Playbook): -> read Notes verbatim before any discovery step; they carry known gotchas for this query family even when no structured choreography exists yet. elif Found AND Results[0].EntityMatch == "exact" AND Results[0].Confidence >= 2: -> skip discovery; fetch live data for Results[*].ResourceID in parallel elif Found AND Results[0].EntityMatch == "partial": -> candidate hint, NOT a hit; read the resource title to validate before trusting elif (any row in Mismatches[] when --debug-mismatches was passed): -> treat as cold start; the stored learning is for a different entity (different canonical resolved from query_entities) else: // Found == false, no playbook, no notes -> cold start; run discovery normally; teach the answer afterward (Step 4). If the family has no playbook yet, that teach auto-synthesizes a playbook candidate from this session's journal - you do not need to record one by hand. Playbook and Notes are orthogonal to the per-resource path. A recall response can carry both a Playbook AND a Results[] hit - use both: the Playbook tells you which choreography to run; the resource hits short-circuit specific steps. Default to skipping mismatches ; pass --debug-mismatches only when investigating cold-start surprises. Candidate judgment details: learnings confirm <id> prints the candidate's full payload before materializing it - check that the printed payload matches the behavior you verified. learnings reject <id> tombstones the derivation signature so the same candidate does not resurface. The envelope carries only the few candidates worth acting on now; jimmy-johns-pp-cli learnings candidates lists the full open set. Graceful degradation: if learnings confirm is an unknown command, you are driving an older binary - ignore the candidates guidance and follow the rest of the protocol. Step 3: always read warnings low_confidence : row exists at confidence<2 . Treat as a hint, not a skip-discovery hit. resource_not_in_store : the local store doesn't have the resource the learning points at. The match validator couldn't classify entities — direct-fetch and re-evaluate. cross_alias_match (per-result): the row was taught under a different alias and matched the live query's canonical via entity_lookups (e.g., a "USA" teach satisfying a "United States" recall). Trust the resource_id. similar_shape_different_entity:<canonical> (top-level): a structurally matching row exists but its canonical entity differs from the live query's. Treated as cold start; the warning carries the conflicting canonical as a hint, but the row is NOT promoted into Results. ambiguous_alias (top-level): a single query entity resolved to multiple canonicals (e.g., "Cards" → Arizona Cardinals + St. Louis Cardinals). Surface the ambiguity from context before committing to a resource. candidates_present (top-level): the envelope carries a candidates section. Handle it via the candidates branch in Step 2 before anything else. lookup_refresh_available (top-level): an entity in the query has no lookup row yet, but synced data could provide one. Run jimmy-johns-pp-cli sync to refresh entity lookups. Top-level no_learnings_for_query_family : the table had no rows above the Jaccard floor. Pure cold start.