The collaboration spine for AI-native teams.

Calm coordination for work and review, without scattered chat fragments.

Request invite →
How AI-native teams use it

From agent output to human decision.

AI tools keep working in your IDEs. FluxDesk gives the team one calm place to review, route, and close the loop.

1. AI tools keep working where they are
Claude Code, Cursor, Aider, GitHub, and teammates can keep producing drafts, reviews, PR notes, and handoffs.
2. Output enters a scoped review path
Tasks, blockers, reviews, and AI-assisted notes are organized by project and work item instead of scattered across chats and tools.
3. Humans approve, route, or hand back
Owners and reviewers can see what is waiting, what is blocked, and which decision needs to happen next.
Why now

AI-native teams have more output than coordination.

The hard part is no longer generating work. It is knowing what changed, who should review, and where the decision should live.

Scattered AI output
Code, docs, summaries, and review notes appear in IDEs, PRs, chats, and task tools without a single review path.
Hidden blockers
Stuck points should surface by work item, not by watching people. No activity rankings, no hours-online stats.
Review handoff
Items pending sign-off need one place to land so delivery does not stall at the final human decision.
Principles

Useful AI coordination still needs boundaries.

FluxDesk is designed around coordination, review, and project context, not employee monitoring.

Coordinate work, not people rankings
Keep AI-assisted output labeled and reviewable
Daily sync is a collaboration signal, not attendance
AI assistants act through the user's scoped permissions
Project data is isolated by default
We do not build CRM, ERP, time tracking, or employee scoring
Why FluxDesk

We do not compete with your IDEs.

Claude, Cursor, Aider, GitHub, Linear, and Notion keep doing execution and storage. FluxDesk handles the coordination state around them.

Execution
Claude Code · Cursor · Aider
  • Generate code, docs, and review notes
  • Work inside IDEs and coding flows
  • Focus: "can the work be produced?"
  • Coordination often stays scattered
Records
GitHub · Linear · Notion
  • PRs, issues, docs, and project records
  • Strong systems of source truth
  • Focus: "where does the artifact live?"
  • Handoffs still need a shared path
Coordination spine
FluxDesk
  • AI-assisted work and human review on one path
  • Project-scoped access and visible ownership
  • Focus: "what decision is next?"
  • No attendance tracking or people scoring
AI assistant access

Connect an assistant without widening its permissions.

Agent access uses personal Bearer tokens over MCP. The assistant can only see and act as the issuing user; writes are audited and AI-assisted content is labeled.

AI Assistant / Agent access (MCP)
Claude Code, Claude Desktop, Cursor, and other MCP-compatible tools can connect through user-owned tokens. Start read-only, narrow scopes, then enable writes only where the user has permission.
External messages
Project updates, mentions, reviews, meeting reminders, and system notices can route through the inbox and connected channels with source labels, read state, and quieter defaults.
Webhook · Push to your endpoint
Self-hosted systems can receive signed inbox events, tune retry behavior, and disable failing endpoints automatically. Use it to connect FluxDesk to your existing operational tools.
Who it's for

Built first for teams that build with AI.

FluxDesk fits small AI-native teams and multi-client collaborators who need review, handoff, and project context without surveillance.

Fits
  • AI-native startups and product teams using Claude Code, Cursor, Aider, or similar tools
  • Remote teams that need one path for blockers, reviews, PR notes, and handoffs
  • Freelancers and consultants serving multiple clients or trust contexts
  • Privacy-conscious teams that reject attendance tracking and employee scoring
  • Teams already using GitHub, Linear, Notion, or chat and missing a coordination layer
Not for
  • Attendance, time tracking, or productivity scoring
  • Performance ranking, people analytics, or hidden monitoring
  • Sales CRM, ERP, or generic back-office process suites
  • Marketplace, paid matching, ratings, or task brokerage
  • Teams that want every human action turned into behavior audit data
Dogfooding

We use it every day.

FluxDesk is built by FluxPrimeStudio — a 19-person team distributed across China, Hong Kong, Japan, Singapore, Thailand, the US, Malaysia, and Spain. We use it to manage cross-timezone collaboration, route AI-assisted handoffs, and keep review decisions visible.

19
Team
8
Countries / regions
100%
Async-first

Ready to coordinate
with AI?

Open to early teams · invite-only. Bring your current tools; FluxDesk adds the review and handoff path around them.

Request invite Member sign in

Building AI collab tools?Join us →