docs: the README describes two engines, not one

README.mdmodified+44-19

Changes to README.md

		@@ -1,15 +1,18 @@
1	1	# Uplink
2	2
3		-Text your Mac from anywhere, even over satellite with no data, and Claude answers.
	3	+Text your Mac from anywhere, even over satellite with no data, and an agent answers.
4	4
5	5	Newer iPhones can send iMessages over satellite when there is no cell or Wi-Fi signal, but nothing
6		-that needs the internet works. Uplink turns those texts into a way to reach Claude: it watches
7		-Messages on this Mac for texts from you, runs each one through Claude Code (on your Claude Max
8		-login, no API key), and texts the answer back.
	6	+that needs the internet works. Uplink turns those texts into a way to reach a coding agent: it
	7	+watches Messages on this Mac for texts from you, runs each one through Claude Code or Codex (on the
	8	+plan you already have, no API key), and texts the answer back.
	9	+
	10	+Claude Code is the default. `UPLINK_ENGINE=codex` changes it for the whole installation, the
	11	+menubar has a picker, and texting `codex` or `claude` switches one thread.
9	12
10	13	- "Whats the NFL score rn?" gets a web search and a two-line answer.
11		-- "please improve ~/Code/stacks with feature xyz" runs a full Claude Code session inside
12		- `~/Code/stacks`, with that repo's CLAUDE.md, hooks and settings, and texts you a summary.
	14	+- "please improve ~/Code/stacks with feature xyz" runs a full agent session inside
	15	+ `~/Code/stacks`, with that repo's agent instructions, hooks and settings, and texts you a summary.
13	16	- Follow-ups continue the same conversation until you text `new`.
14	17
15	18	## How it works
		⋯3 linesShow the 3 lines above this hunk@@ -19,7 +22,8 @@ iPhone --(iMessage, maybe via satellite)--> Messages on this Mac --> ~/Library/M
19	22	|
20	23	Uplink.app polls it every 2s (Full Disk Access)
21	24	|
22		- claude -p ... --resume <thread session> (in the named repo)
	25	+ claude -p ... or codex exec resume ... (in the named repo)
	26	+ whichever this thread is set to
23	27	|
24	28	iPhone <------------------------- Messages (AppleScript) <------- the reply, as plain text
25	29	```
		⋯1 lineShow the 1 line above this hunk@@ -27,8 +31,8 @@ iPhone <------------------------- Messages (AppleScript) <------- the reply, as
27	31	- **Who can command it:** only direct (never group) chats with an allowed handle. By default that is
28	32	this Mac's own Messages handles, so you text yourself. `UPLINK_ALLOWED` sets it explicitly. A
29	33	message is honored only if it passes `app/Uplink/filter.ts`; everything else is ignored.
30		-- **One task at a time per thread.** A second task queues. `status`, `stop`, `new`, `more`, `ping`
31		- and `help` are answered immediately and never queue.
	34	+- **One task at a time per thread.** A second task queues. `status`, `stop`, `new`, `more`, `ping`,
	35	+ `help`, `claude` and `codex` are answered immediately and never queue.
32	36	- **Built for a thin link:** plain text, short answers, long replies split into up to 3 texts with
33	37	the rest behind `more`, a "Working on it" after 20s and a progress line every 10 minutes.
34	38	- **Replies start with ��**, so they stand apart in a thread with yourself, and so Uplink never
		⋯5 linesShow the 5 lines above this hunk@@ -40,10 +44,16 @@ iPhone <------------------------- Messages (AppleScript) <------- the reply, as
40	44
41	45	**[Download Uplink for Mac](https://github.com/stacksjs/uplink/releases/latest/download/Uplink.dmg)**
42	46	(macOS 13 or later, signed and notarized). Drag it to Applications and open it: the menubar walks you
43		-through Full Disk Access, signing in to Claude with a token from `claude setup-token` (kept in your
44		-Keychain), and who may text it. Then text yourself `ping`.
	47	+through Full Disk Access, signing in to the agent you picked, and who may text it. Then text
	48	+yourself `ping`.
	49	+
	50	+You need one of the two CLIs and a plan for it:
45	51
46		-You need the [Claude Code CLI](https://docs.claude.com/en/docs/claude-code) and a Claude plan.
	52	+- [Claude Code](https://docs.claude.com/en/docs/claude-code), the default. The menubar takes a
	53	+ long-lived token from `claude setup-token` and keeps it in your Keychain.
	54	+- [Codex](https://developers.openai.com/codex/cli). Sign in once on the Mac with `codex login`, or
	55	+ `codex login --device-auth` over SSH. Codex keeps its own credentials, so Uplink stores nothing
	56	+ and needs no API key either.
47	57
48	58	Uplink answers texts once it is activated: [$1.99 a month, $19.99 a year, or $29.99
49	59	once](https://uplink.stacksjs.com/pricing), and a code gets six months of Monthly free. The
		⋯28 linesShow the 28 lines above this hunk@@ -78,7 +88,8 @@ its Full Disk Access grant is separate from the downloaded app's):
78	88
79	89	2. **Grant Full Disk Access to Uplink (source)** in System Settings > Privacy & Security.
80	90
81		-3. **Sign in to Claude** with a long-lived token for a background service:
	91	+3. **Sign in to the agent you want.** For Claude Code, a long-lived token, because a background
	92	+ service cannot answer a browser prompt:
82	93
83	94	```bash
84	95	claude setup-token
		⋯3 linesShow the 3 lines above this hunk@@ -88,6 +99,16 @@ its Full Disk Access grant is separate from the downloaded app's):
88	99	./buddy env:set CLAUDE_CODE_OAUTH_TOKEN "$(pbpaste | tr -d '[:space:]')"
89	100	```
90	101
	102	+ For Codex, sign in once and it keeps its own credentials:
	103	+
	104	+ ```bash
	105	+ codex login # or: codex login --device-auth, over SSH
	106	+ ```
	107	+
	108	+ ```bash
	109	+ ./buddy env:set UPLINK_ENGINE codex
	110	+ ```
	111	+
91	112	4. **Check it**, then text yourself `ping`:
92	113
93	114	```bash
		⋯25 linesShow the 25 lines above this hunk@@ -119,18 +140,22 @@ Pushing to `main` deploys https://uplink.stacksjs.com once CI passes (`.github/w
119	140	| `./buddy uplink:watch` | The watcher itself, in the foreground (needs Full Disk Access for your terminal) |
120	141	| `./buddy dev` | The dashboard: setup status, what it is doing, recent texts |
121	142
122		-Configuration lives in `.env`; see the `UPLINK_*` block in `.env.example`. The service picks up edits by itself.
	143	+Configuration lives in `.env`; see the `UPLINK_*` block in `.env.example`, which covers both
	144	+engines (`UPLINK_ENGINE`, `UPLINK_CLAUDE_BIN`, `UPLINK_CODEX_BIN` and the rest). The service picks
	145	+up edits by itself.
123	146
124	147	## Layout
125	148
126	149	- `app/Uplink/`: the daemon (`uplink.ts`), the chat.db reader (`messages-db.ts`,
127		- `typedstream.ts`), the command filter (`filter.ts`), the Claude Code engine (`engine.ts`),
128		- replies (`sender.ts`, `format.ts`), the launchd service and app bundle (`service.ts`,
129		- `launcher.ts`) and setup checks (`doctor.ts`).
	150	+ `typedstream.ts`), the command filter (`filter.ts`), the words it answers itself (`commands.ts`,
	151	+ including `claude` and `codex`), the two engines and the choice between them (`engine.ts`,
	152	+ `codex-engine.ts`, `engines.ts`), replies (`sender.ts`, `format.ts`), the launchd service and app
	153	+ bundle (`service.ts`, `launcher.ts`) and setup checks (`doctor.ts`).
130	154	- `app/Commands/Uplink.ts`: the `buddy uplink:*` commands.
131		-- `app/Models/`: `Conversation` (a thread and its Claude session) and `Run` (one text, one run).
	155	+- `app/Models/`: `Conversation` (a thread, its agent session and which agent) and `Run` (one text,
	156	+ one run).
132	157	- `resources/views/index.stx`: the dashboard.
133		-- `tests/unit/uplink/`: against a real chat.db-shaped SQLite file and a stub `claude`.
	158	+- `tests/unit/uplink/`: against a real chat.db-shaped SQLite file and stub CLIs.
134	159
135	160	```bash
136	161	./pantry/.bin/bun test tests/unit/uplink