Connect a project
Choose the code to work with. Then configure the project environment and choose how tasks run, yourself or with an agent's help.
Quick setup with an agent
Create a chat with your project as its working directory and send the prompt below. The agent will inspect the repositories, propose settings and ask about anything it cannot determine from the code. You do not need to fill in paths and commands manually in this guide.
Verification and acceptance recommendations are collected in a separate guide.
Help me connect this project to GrigDesk pipelines.
Read the documentation for this installed GrigDesk version: new project setup, the profile contract and the standard pipeline-sample. Find this installation's actual profile and published route directories.
Read the recommendations for profiles and routes: /docs/projects/recommendations/. Apply them to environment checks, review and audit instructions, acceptance evidence and rework transitions. In your final report, explain how they apply to this project and what remains unverified.
Inspect the code to identify the stack, repositories, build and relevant test commands, product rules and how to verify the result. Ask only for missing details. Propose the environment mode, runners and models, acceptance points and delivery.
Prepare a local profile from the standard sample if it fits. Connect its repositories and configure the routes we need. Preserve existing settings. Validate the configuration and routes before publishing, then check host readiness without sending model tasks. Agree on a real trial run separately.
Finish by showing what is configured, which checks passed and what you need from me to start the first task. Keep secrets and keys outside the project repository.The sections below explain each part. Fields and files are covered in the profile reference.
Project: where your code lives
A project groups a name and working repositories. It lets you select code in chats, the file editor and tasks. One project can include backend and frontend in separate repositories.
Under Projects, create a record, add existing directories on the server machine and select the primary repository. Registration stores paths; your source files stay where they are.
You can already use the project for coding chats. Pipelines also need a profile.
More about projects and repositories
Profile: how to work with the project
A profile tells GrigDesk how to prepare a working copy, run checks, open a preview and assign work to runners. For example, it defines backend test and frontend build commands.
The profile also defines available routes and how to choose them. It can use an isolated task environment (isolated) or an existing working copy and prepared preview (shared).
For command stages, the profile declares allowed commands to the editor. Agent-assisted setup includes this connection; a ready-made route does not add your stack's commands by itself.
Configure a profile: files, environment, runners and commands
Route: how a task reaches its result
A route defines the workflow: for example, planning, implementation, checks and human acceptance. Bug fixes and new features can use different routes from the same profile.
The profile may contain route source files and instructions. Published versions live in a separate store; a run uses the selected, pinned version. Profiles and routes are configured together but have different responsibilities.
Create a route · Configure stages and instructions
Check readiness
- The project points to accessible repositories on the selected machine.
- The profile is checked: its environment, runner and project commands are ready.
- The route is published and available to select.
Configuration and environment checks are covered in the profile reference. Then choose a small task with a clear expected result and try the first run.