PromptConnext for VS Code

Your assigned PromptConnext tasks, the project's AI coding rules, and a way to close a task without leaving the editor.

The cloud plans; you implement. This extension pulls the tasks assigned to you, shows the coding rules the project was seeded with, hands a task to whichever AI assistant you already run, and marks the task implemented when you commit.

What it does

My Tasks — every task assigned to you, across every workspace you belong to, grouped by project. Tick the checkbox to mark one implemented, or use PromptConnext: Set Task Status… for the full set of states.

Project Context — AGENTS.md, docs/conventions.md and .specify/memory/constitution.md, read from your clone. These are the same files your coding agent reads, and they are yours to edit — the cloud seeds them once and never overwrites them. If the cloud's constitution has moved on since seeding, the view says so.

Copy Task Context — assembles the task, its acceptance criteria, the relevant spec excerpt and the project's coding rules into your clipboard, ready to paste into any assistant. Works offline, works in every editor, works when nothing else does.

Close a task from a commit — commit T3: add retry and the task closes in the cloud with the commit attached as evidence. T003 and T3 mean the same task. A Revert "…" does not re-close anything. Turn it off with promptconnext.closeTasksFromCommits.

Setup

PromptConnext: Sign In — signs you in through your browser. If the redirect never comes back (common on Linux, where the URL scheme is often unregistered), choose Paste code instead.
Open a clone of a project's repository. The extension offers to link the folder when a git remote matches one of your projects, and writes promptconnext.projectId into .vscode/settings.json. A project id is not a secret — commit it so your team shares it.

Settings

Setting	What it is
`promptconnext.cloudApiUrl`	The cloud API. Point at `http://localhost:8080` for local development.
`promptconnext.cloudWebUrl`	The web app that hosts the sign-in pages.
`promptconnext.supabaseUrl` / `supabaseAnonKey`	Real authentication. Leave empty and the extension talks to a cloud running in stub auth mode.
`promptconnext.projectId`	Which cloud project a folder belongs to. Set by Link This Folder to a Project….
`promptconnext.closeTasksFromCommits`	Close tasks from commit subjects. Default on.
`promptconnext.commitScanLimit`	How far back to read on a repository's first scan. Default 1000.

Offline

Your task list is cached and renders instantly, including with no network. Status changes you make offline are queued and flush when you reconnect — the status bar shows how many are waiting. Signing out discards the queue, and warns you first.

On Linux with no available keyring, VS Code stores secrets in memory and they are lost when the window reloads. That costs you an occasional re-login; nothing else is affected.

Known gap

If a Tech Lead hand-edits the tasks document in the web app rather than regenerating it, the cloud creates no task rows, and this extension will show nothing for that project. That is a cloud-side gap (ADR 0020), not an extension bug.

Development

pnpm --dir apps/vscode watch      # esbuild, incremental
pnpm --dir apps/vscode typecheck
pnpm --dir apps/vscode test       # node --test, no editor host required
pnpm --dir apps/vscode package    # produces a .vsix

Then press F5 to launch an Extension Development Host.

Testing against a local cloud

No Supabase, no browser handoff — with supabaseUrl empty the cloud runs in stub auth mode and signing in is just a user id.

cd apps/cloud
DATA_BACKEND=memory AUTH_MODE=stub .venv/bin/uvicorn app.main:app --port 8081

node apps/vscode/scripts/seed-local.mjs    # workspace + project + 3 assigned tasks

The script prints the settings to paste into the Extension Development Host's settings.json. Then: PromptConnext: Sign In → enter dev-user → the tree fills.

Port 8081, not the cloud's usual 8080: that port is commonly taken already, and the symptom is not a bind failure but a 404 from someone else's server, which reads like a routing bug in ours. Check with lsof -iTCP:8081 -sTCP:LISTEN -n -P and use PZ_API plus --port to move both halves together if it is busy too.

Host 127.0.0.1, not localhost: uvicorn binds IPv4 only, macOS resolves localhost to ::1 first, and an unrelated IPv6 listener answers instead.

To exercise the commit-close path, link a folder with PromptConnext: Link This Folder to a Project…, then git commit --allow-empty -m "T1: add login retry". Within a couple of seconds the task flips to implemented with the commit attached. T01, T001 and T0001 all mean the same task; T012 is seeded so you can check T12 finds it too; and git commit --allow-empty -m 'Revert "T1: add login retry"' must not re-close anything.

Two things you cannot test this way, both worth knowing before you conclude something is broken:

Automatic link discovery. It matches a folder's git remote against the project's repo_url, and nothing sets repo_url outside real GitHub repo creation at tech-review exit. Locally, link manually — the same code path writes the same setting.
The browser sign-in handoff. Stub mode skips it. To exercise it you need Supabase credentials and pnpm web running, with promptconnext.cloudWebUrl pointed at it.

The memory backend keeps everything in process, so restarting uvicorn wipes the data and you re-run the seed. That is a feature — starting over costs nothing.

There is no sidecar, no bundled runtime and no local server — see ADR 0019. If a change appears to need one, that is the point to stop and raise it.