Files
LexAI/docs/PROGRESS.md
john kevin asprec efdae32ae1
All checks were successful
CI — Website / Website — typecheck, build (pull_request) Successful in 1m1s
fix: serve the website dist so Coolify answers GET /
Nixpacks built Vite but had no production start command, so Coolify returned Cannot GET /.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-08-17 22:27:25 +08:00

1.8 KiB

Progress board

For the owner. What works, how to see it, and what's waiting on you — plain language.

Updated: 2026-08-17 · Overall: Website Coolify 404 is fixed in the repo; needs a redeploy

What works now

  • Chrome extension: select on any page → AI action → Replace/Copy
  • VS Code extension: select in editor → LexAI context menu / Command Palette → selection replaced
  • Website (packages/website): Home, Docs, Contribute, Community — production server answers GET / (this was the Coolify Cannot GET / failure)

See it yourself — website on Coolify

  1. Pull/push this change, then in Coolify set Base Directory to packages/website (no leading slash).
  2. Turn Is it a static site? off.
  3. Either Build Pack: Dockerfile and port 80, or Nixpacks and port 3000.
  4. Redeploy, then open the domain — you should see the LexAI home page, not Cannot GET /.
  5. Docs live at https://your-domain/#/docs.

Local check: npm run website:build then npm run website:start and visit http://127.0.0.1:3000/

Waiting on you

# Decision Options (recommended bold) What it unblocks
1 Redeploy the Coolify website with the settings above Dockerfile + port 80 / Nixpacks + port 3000 public LexAI site
2 Confirm Cursor mid/strong model picker IDs Keep written IDs / send exact picker strings reliable Task dispatch
3 Grammarly reference screenshots? Later / capture into docs/reference/ Chrome UX gauntlet
4 Publish VS Code extension to Marketplace? Stay local for now / set publisher + publish public install

Next up — proceeds without you

  • Optional: VS Code Prompt Builder / style quick-pick / Marketplace packaging when you ask