Separated routes
The landing experience lives at `/`, while the application itself lives at `/workspace/`.
Focused AI product
Rashtra AI keeps the marketing page and the actual chat application separate, so the product feels like a real AI tool instead of a mixed landing template.
What changed
The landing page introduces the platform. The workspace handles the actual conversations without mixing product marketing into the chat interface.
The landing experience lives at `/`, while the application itself lives at `/workspace/`.
Search, history, and conversation actions stay in a left rail that collapses into a drawer on mobile.
Messages, composer, actions, and status are designed around actual conversation flow.
Markdown, tables, and code blocks stay constrained, scrollable, and responsive.
Errors render as clean bordered UI with escaped text and retry actions.
No shadows, no clutter, just spacing, borders, contrast, and disciplined color usage.
Trust and privacy
The frontend stores conversations in the browser, and chat requests stay on the same origin through `/api/chat` to Cloudflare Workers. Keys remain server-side.
IndexedDB and local preferences in the browser
Frontend requests go to same-origin Worker endpoints only
Conversation export and import remain part of the workspace
Keyboard-friendly controls and responsive layouts across mobile, tablet, and desktop
About
Rashtra AI now separates product discovery from conversation work. The result is a cleaner chat experience, better responsiveness, and a more credible AI application feel.
The workspace is optimized for real usage: long responses, prompt iteration, code review, research, summaries, and exportable conversation history.
Go directly to the app