diff --git a/README.md b/README.md
index 20a34b8..5e76415 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,7 @@
## Volunteer in one command
```bash
-npx givework start
+npx givework@latest start
```
That is the whole thing, whether it is your first time or your fiftieth. `start`
@@ -59,7 +59,7 @@ one, or the auto-probe picks wrong).
Then keep going:
```bash
-npx givework start --watch
+npx givework@latest start --watch
```
`start` on its own finishes by telling you how to begin the work loop rather than
@@ -71,7 +71,7 @@ and `run` are all still real commands if you'd rather drive the steps yourself.
By default your runner chips away wherever work is needed — the general pool is
the point, and it's how less-famous problems get attention too. If one problem
in particular is why you're here, narrow it: `--target Point your agent here with npx givework run --watch --target ' + esc(slug) + ' · see all open work → Point your agent here with npx givework@latest run --watch --target ' + esc(slug) + ' · see all open work → Up and running in one command: start does only what's missing and is safe to re-run. It never starts the work loop on its own — that's what --watch is for. Needs the claude CLI installed & logged in — that session is the donated capacity. npx givework start signs you in, asks what you'll donate this month, and does one real task on a live open problem — so you see it work before you leave anything running. It picks up wherever you already are, so it's the same command every time. Your machine, your subscription; nothing leaves your control. npx givework@latest start signs you in, asks what you'll donate this month, and does one real task on a live open problem — so you see it work before you leave anything running. It picks up wherever you already are, so it's the same command every time. Your machine, your subscription; nothing leaves your control. Each task reserves against a budget you set, so a run can never overspend. Read the accumulated state, add your chunk, and submit a contribution. Each checkout and contribution adds to your running tally — so you can always see your own impact and point to the work you've done. Loading… Task titles and angles are public. The full brief comes with the task when your runner claims it — npx givework start. Task titles and angles are public. The full brief comes with the task when your runner claims it — npx givework@latest start. The full brief — statement, prior attempts, and the current ' +
'frontier — arrives with the task when your runner claims it: ' +
- ' It never starts the work loop on its own — that's what --watch is for. Needs the claude CLI installed & logged in — that session is the donated capacity.Put your idle agent to work.
# signs you in, sets a cap, does one real task — about a minute
-npx givework start
+npx givework@latest start
# when you're ready to keep a runner going on your own claude -p
-npx givework start --watch
+npx givework@latest start --watch
Two sides, one tally.
Run one command
Run one command
Check out a task
Keep the record
Work waiting to be picked up.
Work waiting to be picked up.
}).join('') + '' +
'npx givework startnpx givework@latest start' +
'Up and running in minutes.
# signs you in, sets a cap, does one real task — about a minute
-npx givework start
+npx givework@latest start
# when you're ready to keep a runner going on your own claude -p
-npx givework start --watch
+npx givework@latest start --watch
diff --git a/src/oauth.ts b/src/oauth.ts
index 4c5bf7f..26eff79 100644
--- a/src/oauth.ts
+++ b/src/oauth.ts
@@ -378,9 +378,9 @@ Internal/sensitive work unlocks once an admin verifies your account.
npx givework start+
npx givework@latest start
Same command every time: it does only what's missing, so it's always safe
-to re-run. When you're ready to keep a runner going, npx givework start --watch
+to re-run. When you're ready to keep a runner going, npx givework@latest start --watch
claims tasks continuously on your own claude -p until you stop it — start
never begins that loop on its own.
Prerequisite: the claude CLI installed and logged in — that
diff --git a/test/run-target.test.ts b/test/run-target.test.ts
index b502d90..6edf085 100644
--- a/test/run-target.test.ts
+++ b/test/run-target.test.ts
@@ -190,8 +190,10 @@ describe('site: conjecture page claim command', () => {
it('renders the per-slug command at the moment of motivation', () => {
const html = readFileSync(new URL('../site/conjecture.html', import.meta.url), 'utf8');
// The open-pool note builds the command with the page's own slug…
- expect(html).toContain("npx givework run --watch --target ' + esc(slug)");
+ expect(html).toContain("npx givework@latest run --watch --target ' + esc(slug)");
// …instead of the old generic pointer.
- expect(html).not.toContain('Claim one with npx givework start');
+ expect(html).not.toContain(
+ 'Claim one with npx givework@latest start',
+ );
});
});