fluxy-bot 0.12.2 → 0.12.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fluxy-bot",
-  "version": "0.12.2",
+  "version": "0.12.4",
   "releaseNotes": [
     "Adding a way for users to claim their fluxies on the fluxy.bot dashboard",
     "2. ",

package/supervisor/index.ts

@@ -341,7 +341,7 @@ export async function startSupervisor() {
 
     // App API routes → proxy to user's backend server
     if (req.url?.startsWith('/app/api')) {
-      const backendPath = req.url.replace(/^\/app\/api/, '') || '/';
+      const backendPath = req.url.replace(/^\/app/, '');
       console.log(`[supervisor] → backend :${backendPort} | ${req.method} ${backendPath}`);
       if (!isBackendAlive()) {
         console.log('[supervisor] Backend down — returning 503');
@@ -473,7 +473,7 @@ export async function startSupervisor() {
       if (msg.type !== 'app:api' || !msg.data) return;
 
       const { id, method, path: reqPath, headers: reqHeaders, body } = msg.data;
-      const backendPath = (reqPath || '').replace(/^\/app\/api/, '') || '/';
+      const backendPath = (reqPath || '').replace(/^\/app/, '');
 
       console.log(`[supervisor] App WS → backend :${backendPort} | ${method} ${backendPath} (${id})`);
 

package/vite.config.ts

@@ -25,7 +25,7 @@ export default defineConfig({
     proxy: {
       '/app/api': {
         target: 'http://localhost:3004',
-        rewrite: (path) => path.replace(/^\/app\/api/, '') || '/',
+        rewrite: (path) => path.replace(/^\/app/, ''),
       },
       '/api': 'http://localhost:3000',
     },

package/worker/prompts/fluxy-system-prompt.txt

@@ -260,16 +260,16 @@ Your working directory is the `workspace/` folder. This is your full-stack works
 
 ## Backend Routing (Critical)
 
-A supervisor process sits in front of everything on port 3000. It strips the `/app/api` prefix before forwarding to the backend.
+A supervisor process sits in front of everything on port 3000. It strips the `/app` prefix before forwarding to the backend, preserving the `/api/` path.
 
 ```
-Browser: GET /app/api/tasks → Supervisor strips prefix → Backend receives: GET /tasks
+Browser: GET /app/api/tasks → Supervisor strips /app → Backend receives: GET /api/tasks
 ```
 
 **The rules:**
 - **Frontend** fetch calls: use `/app/api/...`
-- **Backend** Express routes: register as `/tasks`, `/health` — NO `/app/api` prefix
-- No exceptions
+- **Backend** Express routes: register as `/api/tasks`, `/api/health` — standard Express convention with `/api/` prefix
+- The `/app` prefix is what distinguishes workspace backend routes from system routes
 
 **Tunnel reliability:** All `/app/api/*` fetch calls from the dashboard are automatically proxied through WebSocket when available. This is transparent — just use `fetch('/app/api/...')` normally. The WebSocket proxy activates automatically and falls back to regular HTTP if unavailable. You don't need to handle this in your code.
 
@@ -367,6 +367,7 @@ There are TWO completely separate password systems in Fluxy. Understanding the d
 POST /app/api/workspace/set-password
 Body: { "password": "the_password" }
 ```
+(The backend route is `/api/workspace/set-password` — the supervisor strips `/app` from the frontend URL.)
 
 **How to remove it:**
 ```

package/workspace/backend/index.ts

@@ -28,7 +28,7 @@ const app = express();
 app.use(express.json());
 
 // Health check
-app.get('/health', (_req, res) => {
+app.get('/api/health', (_req, res) => {
   res.json({ status: 'ok' });
 });