Start with one task

Connect a project, build a clear workflow and follow it through acceptance. Start with a small change whose result is easy to verify.

Read the architecture overview first: where tasks run, how the application connects to the server and when a relay is useful.

Your first project

1. Install GrigDesk. Prepare a Linux machine, dependencies and access to an AI runner.
2. Connect a project. Set up repositories, checks and a way to open the preview environment.
3. Choose a workflow. Features, bugs and performance work require different evidence.
4. Create a route. Prepare instructions and transitions, validate the draft and publish it.
5. Run a task. Review the result in its preview environment and accept the work.

You already have a pipeline

Read stage configuration to change instructions, checks, transitions and runners. Publish changes for new attempts; running attempts keep their pinned route revision.

In loop mode, a lead agent assigns work to a worker and reviews the results. You accept the final result and resolve stops that require a human.

Explore GrigDesk

• Task trackers, inbox and task shelf organize work and incoming requests.
• Pipelines, sandboxes, agents and routes cover automation.
• Chats, code and projects support everyday development.
• Terminal, SSH, databases and Docker provide development tools.
• Plugins extend GrigDesk with installed packages and your own panels.

Four useful terms

Term	Meaning
Project	Repositories and the environment where work happens.
Route	Stages, instructions, checks and transitions.
Project profile	Environment settings, commands, previews and route integration.
Attempt	One execution of a task using a particular route revision.

Learn with examples

• Add a product filter.
• Fix duplicate form submissions.
• Improve search performance.
• Understand the lead and worker loop.

Version 0.1

GrigDesk is evolving. Connecting a project currently requires technical preparation. Read the requirements and limitations before starting.