deploy.sh:
Validated explicit-deploy workflow. Pre-flight checks (local build,
uncommitted changes, server reachability) run on Mac before touching
server. Code pushed to server via 'git push ssh://...' over the
existing SSH connection — no Mac SSH server required. Server does
git reset --hard to the pushed commit, reinstalls deps if
package.json changed, rebuilds dashboard, restarts services, verifies
health. Full troubleshooting guide in file header.
local-dev.sh:
Runs bridge (:3457) and dashboard (:3101) locally on Mac while
reaching Tiger via SSH. Separate ports + separate SQLite DB keep it
isolated from prod (still live on :3100/:3456). Hot-reload in both
layers. Clean Ctrl-C shutdown.
bridge remote mode:
Added TIGER_REMOTE=true support in bridge/src/tiger.ts and chat.ts.
When set, 'docker exec tiger-openclaw' calls are prefixed with
'ssh $TIGER_REMOTE_SSH'. Backward-compatible: VPS leaves TIGER_REMOTE
unset and runs docker locally as before.
Workflow moving forward:
• Edit locally on Mac
• ./local-dev.sh to test against real Tiger
• git commit small + often
• ./deploy.sh to push to production
Chat history now survives hard refresh, tab close, and multi-device use.
Schema:
chat_messages(id, session_id, role, content, meta, created_at)
+ index on (session_id, created_at DESC)
Bridge endpoints:
POST /tiger/chat — unchanged externally, now persists
user + agent messages alongside the
existing LLM dispatch
GET /tiger/chat/history — ?sessionId=X&limit=200 → ordered messages
DELETE /tiger/chat/history — ?sessionId=X → wipe history
Dashboard:
/api/chat/history — proxy route, bridge token stays server-side
contexts/chat-context.tsx — ChatProvider hydrates messages from the
history endpoint on mount; clearChat()
now also hits DELETE /api/chat/history
Design: single-session model for now (DEFAULT_SESSION_ID constant matches
the openclaw agent --session-id used by the dispatch call). Multi-session
support would require session UI + session-aware routing — deferred to a
later feature sprint.
Tradeoff noted: message data is duplicated between our SQLite and whatever
state OpenClaw keeps internally. Chose duplication over coupling — if
OpenClaw session semantics change, dashboard history remains intact.
- Bridge: Express API server with SQLite (projects, tasks, executions, outputs)
- Dashboard: Next.js app rewired from WebSocket gateway to Tiger Bridge HTTP API
- Tasks: Kanban board with drag-drop, project management with CRUD
- Dispatch: Task dispatch to sandbox with file watcher for status updates
- UI: Container health panel, workspace browser, logs viewer, output viewer
Critical fixes:
- Use execInSandbox instead of execOnHost for container operations
- Watch symlink path instead of container-internal path
- URL-encoded params for GET requests instead of body
- PUT/DELETE support added to useBridgeRequest
Sprints 1-5 complete. Ready for VPS deployment.
