Feature Request

Problem

The current sidebar has "Chat / Dashboard / Workflows" as top-level navigation. This puts conversations front and center, but the natural mental model for users is project-first: "I want to work on Project X, then start a chat."

Proposed Solution

Rename "Chat" to "Projects" as the primary navigation entry point. When "Projects" is selected:

• Show a list of registered projects (codebases)
• Allow adding a new project inline
• Clicking a project expands it to show:
  • New Chat button
  • Chat history (conversations scoped to this project)
  • Settings panel: project description + selector for which workflows are available for this project

This makes the project the organizing unit, and conversations/workflows become children of a project rather than top-level concepts.

Benefits

• Clearer mental model: project → workflow → conversation
• Per-project workflow scoping (complements the slash autocomplete feature)
• Easier onboarding: users see their projects immediately

Implementation Notes

• Sidebar restructure: Projects replaces Chat as primary nav item
• Project settings would extend the existing codebase metadata (description field, workflow whitelist)
• Chat history filtered by codebase_id (already available in the DB schema)
• New API field needed: allowed_workflows on the codebase record