What should Codend work on?
How it works
From a task to a pull request in three steps.
Step 1Describe the task
Write what you need in plain words, the way you would tell a teammate.
- Read
auth/callback/route.ts - Planned the change in 2 files
- Tests passed · 24/24
Step 2Codend does the work
It reads your code, plans the change, edits the files and runs your tests.
Fix the login redirect#41
Ready to mergeMerge
Step 3Review and merge
You get a pull request with a summary and passing checks. Merge it when you are ready.
Why Codend
Describe it. Codend builds it.
- Read
auth/callback/route.ts - Planned the change in 2 files
- Tests passed · 24/24
- Pull request #41 opened
Agents turn tasks into code
Describe the work. Codend plans it, writes the change, and runs your tests while you focus on decisions.
Also send expired sessions back to sign-in Change it by describing it.
Reply in the task with what should change, and Codend updates the same branch and pull request.
AccessHeld by you
GitHub• • • • • • • •
Slack• • • • • • • •
Notion• • • • • • • •
mainMerge to mainApprove
Codend asks. It never merges for you.
Review every change.
Codend works on its own branch and opens a pull request, so nothing reaches main until you approve it.
Run log4 runs this week
Update dependencies→ #52
Run end-to-end testsNo changes needed
Run end-to-end tests→ #53
Write the weekly changelog→ #55
Runs on a schedule
Hand off recurring work like dependency updates and nightly checks, then review the results when you’re ready.
Describe it. Review it. Merge it.
FAQ