Projects

GrigDesk screenshot with prepared data and a Russian interface. Grok, GigaCode, Gemini and Qwen in the panel are planned integrations.

A project groups repositories and workspace relationships. Its record tells the application where code lives and which repository to use by default.

Available actions

• Create projects with names, descriptions and labels.
• Add repositories and select the main one.
• Check path readiness and execution profile integration.
• Open routes and start project chats.
• Inspect dependencies, archive projects and restore them.

Record and execution profile

The record stores project information and paths. The execution profile separately defines task launch, commands and previews. A complete record alone does not prepare arbitrary project environments.

Discrepancies between record and profile are shown explicitly to help identify different code copies being used by tools and pipelines.

Archive

Archiving hides a project from ordinary new-work selection while preserving existing attempts and relationships. Dependencies are considered during further actions.

Read project setup. Related screens: code, chats and routes.