The AI software engineer that ships tested pull requests
Give Daniel a bug, a feature or a ticket. It plans the work, edits the code, proves the change with your own tests in an isolated sandbox, reviews its own diff and opens a pull request for you to merge.
How Daniel works
- Describe the work in plain English, paste a GitHub issue or a Jira ticket, or mention
@Danielin Slack. - Daniel plans and codes in an isolated cloud sandbox with your repository, toolchain and tests.
- Every change is proven. A task only completes when your test command passes; existing tests are never edited to get there.
- Self-review, then a pull request. Daniel reviews its own diff like a senior engineer, fixes what it finds and opens the PR on its own branch.
Built for real engineering teams
Side engineer, not a toy
Picks up a teammate's branch, answers review comments on the same PR, and asks only the questions that are genuinely yours.
Honest results
Tasks that change nothing or aren't verified by tests are reported as blocked, never as done.
Works where you work
Built in: GitHub, GitLab, Slack, Microsoft Teams, Jira and Linear. Plus a plugin marketplace with tested one-click connectors, and any MCP server you run.
Runs on your computer too
npx github:2badagoldman/cognitive-daniel opens Daniel locally to work on any folder: repos, documents, file clean-ups.
PR review and security scans
AI analysis of any pull request, one-click fixes, and scheduled security scans with findings by file and line.
Lower cost per fix
Adaptive planning, focused tasks and a turbo execution loop keep each fix fast and cheap.
Frequently asked questions
What is Daniel?
Daniel is an autonomous AI software engineer by Cognitive AI. It turns a bug report or feature request into a tested pull request.
Does Daniel push to my main branch?
No. Daniel works on its own branch and opens a pull request. You review and merge.
Can Daniel work on files on my computer?
Yes. Code repos get an isolated copy and the result arrives as a new git branch. Plain folders are changed only after the work is verified, with every original backed up in ~/.daniel/backups.
How does Daniel compare with Devin?
We published a head-to-head on real open-source bugs, graded by each project's own hidden tests. Read the results.