Getting Started with Clawdify

Step-by-step setup guide for new and existing OpenClaw installations.

Prerequisites
Required

OpenClaw

A running OpenClaw instance on the same machine. Install guide

Required

Node.js 18+

For building and running Clawdify. Check with node --version

Recommended

Tailscale

For secure remote access from your phone or other devices. Clawdify runs on your local network by default — Tailscale extends that securely without exposing ports to the internet. Get Tailscale

Path AFresh OpenClaw — No Existing Projects

You just installed OpenClaw and want to use Clawdify as your project workspace from the start.

1

Install & run setup

git clone https://github.com/rcostica/clawdify.git ~/clawdify
cd ~/clawdify
npm install
npm run setup

The setup wizard auto-detects your gateway token, workspace path, and enables the required chatCompletions endpoint. You'll only need to set a PIN and port.

2

Restart the gateway

openclaw gateway restart

This applies the config change that enables Clawdify to chat with your AI agent.

3

Build and start

npm run build
npm start

Open http://localhost:3000 (or your Tailscale URL) in your browser.

4

Start using it

A General project is created automatically. Click it in the sidebar to start chatting. Create more projects with the + button in the sidebar.

Path BExisting OpenClaw — Already Has Projects & Files

Your OpenClaw agent has been running via Telegram, Slack, or CLI. There are existing workspace files, project folders, and conversation history.

1

Install & run setup

git clone https://github.com/rcostica/clawdify.git ~/clawdify
cd ~/clawdify
npm install
npm run setup

Same as Path A. The wizard detects your existing workspace and configures everything.

2

Restart gateway & start Clawdify

openclaw gateway restart
cd ~/clawdify && npm run build && npm start
3

Discover existing projects

Go to Settings → Discover Projects and click Scan Workspace.

Clawdify will find all folders in your OpenClaw workspace and show them with checkboxes. Select which ones should become Clawdify projects.

💡 Organizing as sub-projects: If your agent created folders likeproject1/seo/, project1/content/, and project1/ads/, you can drag the child folders onto the parent to set up the hierarchy before importing.

📎 External sub-projects: If sub-projects live in separate workspace folders (not nested inside the parent), the parent's file browser will show them as linked virtual directories.

4

Name your instance (optional)

In Settings → Instance, give this Clawdify a custom name (e.g. "Home Server", "Work Agent"). This name appears in the browser tab and when you install the PWA on mobile — useful if you run multiple Clawdify instances.

Remote Access with Tailscale

Clawdify binds to localhost:3000 by default. To access it from your phone or another computer:

  1. Install Tailscale on the server and your device
  2. Both devices join the same Tailscale network
  3. Access Clawdify at http://your-server:3000 from any device on your Tailnet
  4. For HTTPS, enable Tailscale HTTPS

Why Tailscale? It creates a private, encrypted network between your devices. No ports open to the internet, no VPN configuration, no certificates to manage. Your Clawdify instance stays invisible to the public internet.

Troubleshooting

Chat returns 405 Method Not Allowed

The gateway's chatCompletions endpoint is disabled. Run npm run setup again (it auto-enables it), then openclaw gateway restart. Check Settings for the endpoint status.

API errors (500) on first load

Database tables auto-create on first startup. Try restarting Clawdify. If it persists, delete ~/.clawdify/clawdify.db and restart — it will be recreated.

Gateway shows 'Connected' but chat doesn't work

Test the gateway directly: curl -X POST http://localhost:18789/v1/chat/completions -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" -d '{"model":"openclaw:main","messages":[{"role":"user","content":"hi"}]}'

Can't access from phone

Make sure both devices are on the same network (or Tailscale). Check that the PIN is correct. Clear browser cache if you recently updated.