Conjure

Conjure is your commerce and delivery agent: describe what you need, find an eligible retailer, shop, coordinate payment and preparation, and arrange supported delivery. It retains the complete shopping harness.

Install and run

The public package is @conjureing/cli; its executable is conjure. Initial native support is macOS on Apple Silicon and Intel, with Node 22 or later for bundled commerce tools.

npm install -g @conjureing/cli
conjure

Choose a model provider when prompted. Provider credentials are for model access; Conjure accounts, retailer sign-in, payment authorization and delivery-provider access are separate.

The npm scope distinguishes this package from unrelated apps. An executable name is resolved locally through PATH, not reserved globally. The unscoped npm package conjure belongs to someone else; conjureing is a separate SDK.

Your personal profile

Ask Conjure to connect your personal profile. Open the approval link on conjure.ing, sign in with a Conjure passkey and approve the matching terminal code. The agent must not approve its own access.

Conjure's database stores your saved name, contact details, preferences and named addresses. The harness refreshes these before user turns, including after restart. Explicit personal corrections can be saved; a one-off recipient or merchant observation does not replace your defaults. Offline cached details are marked stale and require confirmation before transactions.

Ask to show, change or clear saved details, or disconnect your profile. Revoke a lost device at Conjure profile devices. Another product's accounts, tokens and cached profiles are never imported.

Shopping and fulfillment

Discovery runs through Conjure's hosted service using its own provider configuration. Search results identify candidates; they do not prove branch inventory, basket availability or curbside fulfillment. Inspect the retailer's actual ordering flow.

Kernel is the default merchant browser. Local Chrome requires an explicit choice. Conjure handles browsing and cart building; required merchant login, verification and payment approval remain human actions. Payment credentials stay outside model arguments, transcripts and logs. Unknown checkout outcomes require reconciliation before any retry.

Robomart is an optional external Delivery MCP integration. It supplies robot delivery when available. It is not Conjure's account, discovery, database or backend service. Coverage, fees and parcel limits come from current provider results. For a robot-dependent purchase, verify the supported delivery path before paying and book only after pickup readiness. Notify the retailer when the vehicle actually arrives.

A configured tool or successful local test does not prove a merchant accepted an order or a robot completed a delivery. Report each state accurately.

Development

npm run build:dev
./zig-out/dev/bin/conjure

Use native Zig 0.16.0. On Apple Silicon use the ARM compiler even from a translated terminal. CONJURE_ZIG can select its executable. Follow AGENTS.md for focused tests, serial terminal fixtures and final universal packaging.

Runtime state lives under ~/.conjure/; application overrides use CONJURE_*. Embedded commerce code is materialized into a content-addressed private directory so different builds do not share stale scripts.

Current cutover and publication evidence is recorded in the repository separation ledger. Native automatic updates must not be claimed until Conjure's release origin is verified. Third-party attribution is preserved in LICENSE and THIRD_PARTY_NOTICES.md.

For optional robot delivery, run conjure login robomart and enter the provider credential in the hidden terminal prompt. It is stored separately in ~/.conjure/delivery-robomart.json. Conjure never imports old account credentials or starts a provider Console login. The current external MCP does not expose funding verification: robot-dependent goods purchases stay blocked until a supported fulfillment path is established. Already purchased, verified pickup-ready orders can use the reviewed booking workflow.

If an action reports that its automatic reviewer is unavailable, it has not executed. Enter /permissions ask, retry, and review that exact action in the permission prompt. Model login, Conjure profile approval and checkout approval are separate.

Upgrade with npm install -g @conjureing/cli@latest. Existing merchant orders, browser sessions and delivery idempotency records are preserved. Reconnect your Conjure profile; an older product's cached profile is not imported. Reconnect the same external delivery account before reconciling an existing delivery. Never recreate an uncertain purchase or booking.