@zortexhq/install 0.1.23 → 0.1.24

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -50,37 +50,37 @@ a bare `zortex` starts the same automatic agent onboarding.
50
50
  1. Zortex checks the inherited Codex/Terminal Windows token. It does not ask
51
51
  for broad elevation and does not use a model on the normal path.
52
52
  2. It records a reversible Autopilot receipt, configures its own read-only
53
- Codex MCP bridge, and automatically starts the existing full sync for every
54
- released source in the background. Users do not select sources or request
55
- a preliminary sample.
53
+ Codex MCP bridge, and authorizes every released source. Connection reads no
54
+ messages or files.
56
55
  3. If a provider needs OAuth, Zortex opens the provider page itself. The user
57
56
  completes only password entry, MFA, consent, CAPTCHA, hardware-key touch, or
58
57
  account-risk confirmation in that provider surface. Zortex never asks the
59
58
  user to run a shell command or paste a credential.
60
59
  4. The user may ask a question as soon as authorization is connected. Codex
61
- checks the receipt while background synchronization runs:
60
+ checks the receipt:
62
61
 
63
62
  ```powershell
64
63
  zortex autopilot connect-status <receipt-id>
65
64
  ```
66
65
 
67
- The result includes each source's synchronized count and `backfill` state.
68
- A scoped question uses matching synchronized data and reports incomplete
69
- coverage if catch-up is still running. A question without a range waits for
70
- `caught_up` and analyzes the complete connected corpus.
71
- 5. Codex uses the read-only `indra.context` bridge and cites the returned
72
- Zortex references.
66
+ For each question Codex selects the minimum relevant connected sources and
67
+ runs `zortex retrieve <source> --query <provider-query> --json`. Each read is
68
+ bounded to at most ten matching records; no queryless or account-wide scan
69
+ starts implicitly.
70
+ 5. Codex uses the read-only `indra.context` bridge over those retrieved records
71
+ and cites the returned Zortex references.
73
72
 
74
- There is no ten-item onboarding sample. Full coverage is claimed only when a
75
- source reports `backfill: caught_up`.
73
+ There is no onboarding sample or background backfill. If one bounded query is
74
+ too narrow for the user's request, Codex asks for a narrower scope instead of
75
+ silently scanning the account.
76
76
 
77
77
  ### Supported Windows Autopilot sources
78
78
 
79
- | Source | Sync target | Notes |
79
+ | Source | Connection and question-time read | Notes |
80
80
  | --- | --- | --- |
81
- | `gmail` | Full connected mailbox | Uses the existing read-only Gmail connector and its declared exclusions. |
82
- | `google-drive` | Full connected Drive corpus | Uses the existing read-only Drive connector and its declared exclusions. |
83
- | `outlook` | Full connected mailbox | Uses the unchanged 0.1.19/0.1.20 Outlook connector. |
81
+ | `gmail` | OAuth connection; up to 10 matching messages per query | Uses the existing read-only Gmail connector and its declared exclusions. |
82
+ | `google-drive` | OAuth connection; up to 10 matching files per query | Uses the existing read-only Drive connector and its declared exclusions. |
83
+ | `outlook` | OAuth connection; up to 10 matching messages per query | Uses the existing read-only Outlook connector. |
84
84
  | `notion` | Connector fabrication | No released automatic authorization route yet; request files or joins a D29 build order. |
85
85
  | `posthog` | Connector fabrication | No released automatic authorization route yet; request files or joins a D29 build order. |
86
86
  | `whatsapp` | Deferred | Not part of this Windows Preview. |
@@ -107,8 +107,8 @@ records. Use the product's audited privacy-erasure path for data deletion.
107
107
  repair. Do not paste a credential or run a repair command yourself.
108
108
  - `codex` not found: install/start the local Codex CLI first, then rerun the
109
109
  explicit onboarding command.
110
- - Incomplete all-data answer: wait for each requested source to report
111
- `backfill: caught_up`.
110
+ - Broad question: narrow its date, sender, file name, or subject so a bounded
111
+ provider query can answer it.
112
112
 
113
113
  When Codex invokes the npm launcher with no command, it starts
114
114
  `zortex onboard --agent --host codex`. That scripted onboarding first proves