DenlyLive Chat
Open a project-scoped coding session and follow tools and messages in real time.
Free plan · no card required
Keep coding work moving across every project.
Queue tasks for your existing coding agents, approve their plans, and review pull requests from one dashboard. Work runs on your machines.
For developers and small teams working across repositories with Claude Code, Codex, Cursor, Grok Build, or Antigravity.
Your agent subscription or API key. Your machine stays awake to run work.
Your machineThe agent runs on your own machine. The checkout stays local; selected content is uploaded.
local
Your runtime accountUse a supported subscription or API key. Your provider's limits and charges apply.
yours
Your gatesReview the plan and PR in the supervised flow. Opt in to Autopilot when enabled.
your move
Honest scope
Denly CLI · macOS, Windows & Linux
GitHub & GitLab repos
Optional end-to-end encryption
token billing
Two projects, one place to return to
See what needs your attention. Keep the rest moving.
A checkout fix needs a plan approval. A docs update is ready to review. When a check fails, return to the saved work before approving the result.
Illustrated walkthrough with sample tasks and shortened playback. No live customer data or measured completion times.
New task
Creates the task in Denly. No GitHub issue is opened.
A title is all you need. Everything else has a default.
Cancel
Create
Queue a storefront task with a clear acceptance check.
Follow the two-project walkthroughInspect the example and run its tests
Amber = waiting on you
Teal = done, or the agent's
Where the work runs
Choose where your agent works.
Cloud and local setups have different costs and requirements. Denly coordinates agents that run on your machines.
Cloud execution
An agent hosted by its vendor
Work continues while your machine is off, in an environment the provider operates. The provider needs access to the repository it works on. Usage and billing depend on the service and plan.
Local execution
A runtime CLI on its own
The CLI works in your local environment. Claude Code's native Remote Control may already cover phone and browser access. Denly adds a shared task and review workflow across projects. Compare the setup and decide what you need.
Denly adds a shared dashboard to agents on your machines, with supervised review by default and optional Autopilot.
The task lifecycle
Six steps in the supervised flow.
By default, the agent waits for your plan approval and PR review – amber means it's your move. Workspace owners and admins can also enable Autopilot for tasks that should pass those human gates automatically.
1
You describe
Write the task in plain English
“Add localization (EN / ES / FR).” No labels, no board setup, no ticket template. Point it at a repo and go.
2
Agent works
Your agent reads the repo and posts a plan
Approach, the files it intends to touch, the tests it will run, and the risks – written out before a single line changes. Use Claude Code, Codex, Cursor, Grok Build, or Antigravity, per project.
3
Your move
You approve the plan
In the supervised flow, nothing is built until you say so. Approve the plan, or send it back with notes. The agent can also stop mid-run to ask a question and wait for your answer.
4
Agent works
It builds & tests on your machine
Writes the code, runs the checks you configured for the repository, pushes a branch like agent/task-28 – all on your own machine, against your real toolchain.
5
Your move
You review the pull request
A normal PR with a normal diff and green checks. Read it, comment, request changes – the same review you'd give a teammate.
6
Done
Merge
Merge from the dashboard – or your phone. A task explicitly set to Autopilot can merge after its configured checks pass.
For a local project without Git, review the folder changes and mark the task complete; there is no pull request or merge.
More control when you need it
One lifecycle, with the supporting system built in.
Scoped Skills & Docs
Give each task only the reusable instructions and repository context it needs.
Flows, reviews & schedules
Add custom steps, human gates, multiple reviewers, and recurring work.
Teams & assignments
Share private projects safely and route tasks to the intended teammate.
Multi-repository runners
Use project groups and one machine runner for coordinated work across repositories.
Usage, cost & insights
Track reported quota, tokens, budgets, outcomes, and runtime success.
Integrations
Create agent tasks from your tracker or chat tool – progress, comments, and status flow back automatically. All 15 providers, with a setup runbook each:
The data boundary
Your working checkout stays on your machine.
Your repository is cloned, edited, built and tested on your runner. Selected uploads can contain source code or secrets: READMEs, docs, plan snapshots, transcripts, attachments and no-Git review diffs. Agent output recording defaults to Full, including file and command output; workspace or project policy can choose Text or Off. Optional workspace end-to-end encryption protects supported uploaded content under your passphrase. Without it, that content is readable to the service. Skills remain plaintext for validation. See coverage and known limitations. Your Git host and AI provider also receive the data the work requires under your agreements with them.
Band 1Runs locallyselected content can still be uploaded
Your working checkoutcloned, edited, and tested locally
Your AI key & subscriptionread from your machine only
The runtime processruns locally; recorded output can be uploaded
Band 2 · optionalCiphertext when workspace E2E is enabledend-to-end encrypted under a passphrase only you hold
Task titles & descriptions7b1a·9f…c4e2
Plans, comments & agent conversationse0d3·2a…81bf
Attachmentsencrypted before upload when E2E is on
Band 3Plaintext metadata we seeused to route work and show usage
Task status & timingstage, progress, when it ran
Cost & token numbersthe figures, not the traffic
PR linkspointers to GitHub, not diffs
Who and what ran itassignee, runtime and model, repository name, flow configuration
We hold no copy of your passphrase.
End-to-end encryption is only real if we can't decrypt. We can't – which also means if you lose your passphrase, that encrypted history is unrecoverable. That's the cost of a key only you hold.
The honest trade-off: work runs while your machine is awake.
Because the agent runs on your machine, tasks execute only while that runner is awake and online. Queue work from the dashboard while it is offline and it runs when the runner wakes. That's the direct cost of using your subscription: a coding-agent login is bound to your machine, so “uses my subscription” and “runs in the cloud 24/7” can't both be true.
Setup, end to end
Four accurate steps, then your first task.
No config file, no YAML, no labels to create, no board to set up, no gh auth login.
1
Sign in
GitHub, Google, or an email and password. That's the whole account step.
Continue with GitHub
2
Connect a repository
Choose GitHub, GitLab, or a manual repository. GitHub App access is scoped to the repositories you pick.
storefront
added
3
Install and sign in to the CLI
Follow the platform-specific Quickstart, then run denly login on the machine that will execute work.
denly login ✓
signed in
4
Install the project
Copy and run the dashboard-provided denly install <project-id> command. It clones or adopts the repository, starts the runner, and verifies a live status.
denly install storefront
Then it clones the repo and starts the runner for you – zero config. Describe your first task and the agent picks it up. Every command in one place: the denly CLI reference.
Pricing
Start free. Upgrade when your work grows.
Your plan covers your Denly account and the workspaces you created. Denly charges for the control plane only; AI usage stays directly with its vendor.
Prices shown in USD. Your local currency and taxes are confirmed at checkout.
The plan limits below apply. Nothing you built is ever deleted, and nothing is frozen for storage: past an allowance, new uploads and document saves are refused and everything already there stays readable and keeps running. A change that reduces what your plan covers gets 60 days’ notice, never before the end of a term you have already paid for.
Free
$0forever
For trying Denly on real work.
- Unlimited projects
- 2 machines, one task at a time
- 250 MB of documents and attachments
- 1 person, 1 workspace
- Your own runtime subscription or API key
Pro
For individuals$10/ month
For running a real fleet across machines.
- Unlimited projects and machines
- Tasks in parallel, not one at a time
- 5 GB, pooled across your workspaces
- 1 person, unlimited workspaces
- Your own runtime subscription or API key
Teams
2 seats minimum · 14-day trial$12per seat / month
For teams coordinating multiple products.
- Everything in Pro
- 10 GB + 2 GB per seat, pooled
- Seats are people, not workspaces
- Role-based team access
AI cost is always yours – we never mark up tokens.
There is no token billing, ever. You bring your own runtime subscription or API key; inference is billed to you, by the vendor, at their price. We don't touch it.
Straight answers
The questions a skeptic actually has.
Your working checkout stays on your runner. Selected uploads can contain source: READMEs, docs, plans, transcripts, attachments and no-Git review diffs. Full recording is the default; policy can choose Text or Off. Optional workspace E2E protects supported content; see the security documentation for coverage and known failure paths. Your Git host and chosen AI provider remain outside that boundary.
Claude Code, OpenAI Codex, Cursor, Grok, or Antigravity – on your own subscription or API key. Set it per project or as a workspace default.
Never. Inference is billed to you directly by your runtime provider. Denly's Free plan is $0, Pro is $10/month, and Teams is $12 per seat/month with a 2-seat minimum and a 14-day trial – a seat is one person, however many of your workspaces they are in.
Work runs only while your runner machine is awake and online. Anything queued while it is offline waits and runs when the runner wakes.
Yes. macOS, Windows, and Linux use the same Denly CLI. On Windows, one PowerShell command installs it for your user with no admin rights. After
denly login, the dashboard shows the exact denly install <project-id> command to run.Exactly two: Contents and Pull requests, scoped to the repos you pick when you install the GitHub App. That's all – no org-wide access, no admin.
In the supervised flow, you approve the plan and review the pull request before merging. A workspace owner or admin can enable Autopilot, which a task creator may choose for an eligible task. A Git-backed task using Autopilot can pass those human gates and merge automatically after its configured checks. Questions, failed checks and merge failures still stop for a person.
Point it at a repo and close the dashboard.
Start free with no card. No token markup, no config file.