AutoCua
Automate with computer-use agent (ComputerUse / CUA) for macOS, Windows, Linux, Browser, iOS & Android. It sees the screen, clicks, types, browses and writes the code too. One agent, every computer.
Multi-user Kanban board
Translation pending
ProductivityTypeScript · JavaScriptGitHub @MilluherOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Multi-user Kanban board built with Next.js, Express, Prisma, and Socket.io
Loading the full README. The saved excerpt is shown below.
4. Point the frontend at your local backend
frontend/src/lib/api.ts hardcodes the deployed API, so a local frontend talks to
the deployed backend rather than the one you just started. Change baseURL to
http://localhost:4000/api (or whatever PORT the backend logs) while working
locally.
Sign in. npm run db:seed creates one admin user, [email protected], with the
password set in backend/prisma/seed.js. Change it after your first sign-in —
that password is committed to this repository, and the account is the super-admin
that the admin screens exempt from every guard.Read the full README ↗cd backend && npm install
cd ../frontend && npm install
cd backend
npm run db:push
npm run db:generate
npm run db:seed
Terminal 1 (Backend):
cd backend && npm run dev
Terminal 2 (Frontend):
cd frontend && npm run dev
frontend/src/lib/api.ts hardcodes the deployed API, so a local frontend talks to
the deployed backend rather than the one you just started. Change baseURL to
http://localhost:4000/api (or whatever PORT the backend logs) while working
locally.
Sign in. npm run db:seed creates one admin user, [email protected], with the
password set in backend/prisma/seed.js. Change it after your first sign-in —
that password is committed to this repository, and the account is the super-admin
that the admin screens exempt from every guard.
The seed only runs against an empty database: it counts users first and skips if any exist. So it will not reset a password or recreate a user you deleted, and it is safe to leave in the backend's start command.
Every in-app notification (ticket assigned, @mention, PRD approval requested,
PRD section to complete, PRD approved, PRD changes requested) is also emailed to
the recipient through Resend. Email is best-effort: if it
fails, the error is logged and the in-app notification still goes out. The code
is in backend/src/lib/email.js.
Backend environment variables (Railway → backend service → Variables):
| Variable | Required | Notes |
|---|---|---|
RESEND_API_KEY | yes | From Resend → API keys. Without it, emails are skipped. |
EMAIL_FROM | for real use | e.g. FluxusTeam <[email protected]>. Must be on a domain verified in Resend. The default [email protected] only delivers to the Resend account owner's own inbox. |
FRONTEND_URL | no | Base for links in emails. Defaults to https://fluxusteamkanban.vercel.app. |
EMAIL_NOTIFICATIONS | no | Set to off to pause emails without removing the key. |
The sending domain does not have to be the app's domain: the app can stay on
vercel.app while mail is sent from a domain you own (e.g. fluxx.ng), once
that domain's DNS records from Resend → Domains are added at its registrar.