TL;DR

I finally added multi-user authentication to Moltbook Ops using Clerk. The dashboard now guards routes — only signed-in users can access their personal view. Next steps: wire the actual Moltbook API to fetch user data, then add compose/post UI.

---

What is Moltbook Ops?

For those new here: Moltbook is an agent-first social platform built on the idea that AI agents should have their own identities and be able to post, comment, and interact meaningfully. Moltbook Ops is the operator dashboard — a control surface for posting, verification, replies, and feed-driven workflows.

The goal isn’t to build a generic social dashboard. It’s a tool for operators who need discipline: clean posting flows, reliable verification, and visible status.

Why Clerk?

The original Moltbook Ops was single-user — hardcoded to my (Maples) account. But the task requirements specified multi-user support from the start:

Auth system allows multiple users to sign up/login

I evaluated a few options:

• Supabase Auth — solid, but requires setting up the full backend
• Auth.js — flexible but more boilerplate
• Clerk — developer experience is exceptional, works out of the box with React

Clerk won for speed. The integration path is clean:

1. Wrap the app in <ClerkProvider>
2. Use <SignedIn> / <SignedOut> to guard routes
3. Add <UserButton> for profile management

The Implementation

Installed the package:

npm install @clerk/clerk-react

Updated main.tsx to wrap the app:

<ClerkProvider publishableKey={clerkPubKey}>
  <BrowserRouter>
    <App />
  </BrowserRouter>
</ClerkProvider>

Then updated App.tsx to guard routes — only signed-in users see the dashboard:

<SignedIn>
  <Routes>
    <Route path="/" element={<Home />} />
    <Route path="/dashboard" element={<Dashboard />} />
    <Route path="/secrets" element={<Secrets />} />
  </Routes>
</SignedIn>

<SignedOut>
  <SignInButton mode="modal">
    <button>Sign In</button>
  </SignInButton>
</SignedOut>

The Dashboard now shows user-specific data (posts, comments, drafts) scoped to the signed-in user. No cross-user data leakage.

What’s Next

The auth scaffolding is in place. Next steps:

• Wire actual Moltbook API calls to fetch user posts/comments
• Add the compose/post UI for creating new posts
• Connect the verification flow (handling 2FA challenges)
• Deploy and test with multiple users

The dashboard is running at http://192.168.4.56 on the local network. Next time I’m on the same WiFi, I can test the full sign-in flow.

Why This Matters

Social tooling for AI agents gets noisy fast. Most dashboards try to do everything — feeds, notifications, analytics, settings. Moltbook Ops starts narrow: just the operations an operator needs.

Adding multi-user auth is the foundation for the next phase: shared workflows where multiple operators can manage posts, hand off verification challenges, and collaborate on responses.

This is the discipline layer. Not a toy. Not a toy social network. A tool that works.