Denly

Quickstart: your first coding-agent task from your own machine

Install and authenticate a runtime, install Denly, connect a project, enroll and verify its runner, then create a task and review its pull request or no-Git folder changes.

  1. Prepare a runtime. On the computer that will do the work, install and authenticate one supported runtime: Claude Code, Codex, Cursor, Grok Build, or Antigravity. Follow the vendor’s installation and sign-in steps, for example Claude Code setup or Codex CLI setup. Use its own CLI login or supported API-key setup, then confirm it can run locally. The runtime guide lists the choices. denly login signs into Denly; it does not sign into your runtime.
  2. Install Denly. Follow the platform installation instructions. On macOS or Linux run curl -fsSL https://denly.dev/install.sh | sh; on Windows PowerShell run irm https://denly.dev/install.ps1 | iex. Check denly --version.
  3. Connect your project. Sign in and create or join a workspace. Use App bar project switcher → Add a project. Connect GitHub, GitLab, or a manual repository, or choose Local project · no Git. For no-Git, optionally choose an exact runner folder; otherwise it uses ~/Denly/<project-id>.
  4. Enroll the computer. Run denly login and approve the displayed code in your browser. Copy the dashboard’s exact denly install <project-id> command. It clones the Git project or creates/adopts the no-Git folder, enrolls the runner and starts it. Use the actual project ID in place of my-project below.
  5. Verify readiness. Run denly status my-project and denly doctor my-project. Confirm a fresh machine report in the dashboard and select an installed, authenticated runtime. Keep that computer awake and online; queued work waits while it is offline.
  6. Create the first task. Select the project, press New task, enter a small request such as “Add setup instructions to the README”, select yourself as assignee and your runtime/model, and start with planning. Open the task and approve its plan, or reply with changes.
  7. Review the result. After the build and configured checks, a hosted Git project provides a pull request: review its diff and checks, request revisions if needed, then merge. A no-Git project applies edits directly in its runner folder: open Review changes, inspect the file list/diff and the local files, request revisions if needed, then choose Approve local changes. There is no separate Apply button, branch, pull request or merge for no-Git projects.
Enroll and verify (replace my-project)
denly login
denly install my-project
denly status my-project
denly doctor my-project