OpenClawDashboard

History

Manohar Gupta 6621c6b28b feat(chat): server-side persistence via SQLite 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.		2026-04-18 19:10:47 +00:00
..
public	feat: initial commit with dashboard, docs, and configurations	2026-02-10 20:54:37 +05:30
src	feat(chat): server-side persistence via SQLite	2026-04-18 19:10:47 +00:00
.gitignore	feat: initial commit with dashboard, docs, and configurations	2026-02-10 20:54:37 +05:30
components.json	feat: initial commit with dashboard, docs, and configurations	2026-02-10 20:54:37 +05:30
eslint.config.mjs	feat: initial commit with dashboard, docs, and configurations	2026-02-10 20:54:37 +05:30
next.config.ts	feat: initial commit with dashboard, docs, and configurations	2026-02-10 20:54:37 +05:30
package-lock.json	feat: complete Tiger dashboard implementation	2026-04-12 23:27:51 +05:30
package.json	feat: complete Tiger dashboard implementation	2026-04-12 23:27:51 +05:30
postcss.config.mjs	feat: initial commit with dashboard, docs, and configurations	2026-02-10 20:54:37 +05:30
README.md	feat: initial commit with dashboard, docs, and configurations	2026-02-10 20:54:37 +05:30
tsconfig.json	feat: initial commit with dashboard, docs, and configurations	2026-02-10 20:54:37 +05:30

README.md

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

Next.js Documentation - learn about Next.js features and API.
Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.