GrigDesk 0.1
GrigDesk is actively evolving. Its primary use case is one developer working on their own Linux machine. Project and pipeline setup requires technical preparation.
Available workflows
- Run tasks through configurable agent and command stages.
- Approve plans, inspect results and return work with feedback.
- Draft, validate and publish route revisions.
- Use a lead and worker loop until human acceptance.
- Open task previews when the profile prepares them.
- Chat with agents and use development tools in one application.
Requirements and limits
| Area | Considerations |
|---|---|
| System | The installation guide targets Linux and user systemd services. |
| Projects | A profile must define commands, environments and preview integration. Universal setup for arbitrary stacks is not claimed. |
| Runners | AI CLIs must be installed and authenticated. Available models depend on the tool and account. |
| Board | The board and inbox task creation use Bitrix24. Chats do not require a portal. |
| Previews | Isolated environments depend on project configuration; containers need Docker. |
| AI results | Acceptance criteria, checks and human decisions remain part of the workflow. |
| Loop mode | Handoffs have a profile limit. Lack of progress requires human review. The stall arbiter and automatic rethink do not work in loop mode. |
Locality and cost
The server runs on your chosen Linux machine. The application can connect directly to an accessible remote server; a relay can provide mobile access to a home PC behind NAT. Read architecture.
Cloud runners send their provided context to the provider. Chats can use local Ollama models.
GrigDesk is distributed under MIT. Models and infrastructure use the terms of your chosen services and your own keys or subscriptions.
Learning examples
Site examples use prepared data. They do not execute real tasks, call GrigDesk or indicate AI execution speed. Recipes need adaptation to your profile and are not presented as verified importable configurations.
Documentation and updates
Review version instructions and preserve a working configuration before updating. The main guides were verified on 25 September 2026, loop mode on 29 September, and branding, architecture and installation on 19 October.
Sources: repository, route editor, project setup and engine.
Report a problem
Open a GitHub issue with your version, expected and observed behavior, reproduction steps and relevant errors. Remove keys, passwords and private project data from attachments.