AI Software Engineer
aka “Software Engineer” in the catalog
The moment a PR opens it is reviewed; tagged issues become tested draft PRs, and review comments or red CI on its own PRs get fixed on the branch. Errors traced to a suspect line, upgrades drafted, a Friday client report.
- Category
- Engineering
- Scheduled tasks
- 8daily, weekly
- Runtime
- Hermes
- Works with
- GitHubSentryLinearJiraSlackSnykDatadogFirecrawlNotion
- Hosting
- Fully managed, always on
- Weekly Client ReportWeekly on Friday at 16:00
- Ticket Pickup SweepWeekdays
- PR Review SweepWeekdays
- Error Triage SweepDaily
- Daily Engineering BriefWeekdays at 08:30
- Weekly Upgrade SweepWeekly on Monday at 06:30
- Doc Drift CheckWeekdays at 07:00
- Critical CVE WatchDaily
- Mon
- 06:30Weekly Upgrade Sweep
- 07:00Doc Drift Check
- 08:30Daily Engineering Brief
- Tue
- 07:00Doc Drift Check
- 08:30Daily Engineering Brief
- Wed
- 07:00Doc Drift Check
- 08:30Daily Engineering Brief
- Thu
- 07:00Doc Drift Check
- 08:30Daily Engineering Brief
- Fri
- 07:00Doc Drift Check
- 08:30Daily Engineering Brief
- 16:00Weekly Client Report
The moment it happens.
The AI Software Engineer does not wait for its next scheduled check. Connect a trigger and it starts the second the event arrives. Until you do, its schedule covers the same work.
GitHub webhook
When: PR opened
Review saved minutes after a pull request opens or gets new commits
GitHub webhook
When: Issue labeled
Tagged GitHub issue picked up and shipped as a tested draft PR
Signed webhook
When: Linear issue tagged
Tagged Linear issue picked up and shipped as a tested draft PR
Signed webhook
When: Error alert
New production error traced to a deploy and a suspect line within minutes
GitHub webhook
When: Vulnerability alert
Critical CVE in a dependency judged for exploitability and flagged at once
GitHub webhook
When: Push to default branch
Docs pages a merged change made wrong get corrections drafted the same hour
GitHub webhook
When: PR feedback or mention
Review comments on its own PRs fixed on the branch; a team mention taken as a ticket
GitHub webhook
When: CI failed
Red CI on its own PR fixed when tests pass; a red main traced to the likely commit
How the AI Software Engineer works
Every run reads from the tools you connect, works through its brief, and keeps what it learns in a persistent workspace, so context carries forward instead of starting from scratch.
Connect the ones you use. It works with what it has.
- Weekly Client ReportWeekly on Friday at 16:00
- Ticket Pickup SweepWeekdays
- PR Review SweepWeekdays
- Error Triage SweepDaily
- Daily Engineering BriefWeekdays at 08:30
- Weekly Upgrade SweepWeekly on Monday at 06:30
- Doc Drift CheckWeekdays at 07:00
- Critical CVE WatchDaily
Keeps in its workspace
- Who the owner is: business, timezone, quiet hours, delivery channel, which duties matter most
- Who the work is for: business or agency mode, client name, report reader, sign-off and tone for the weekly report
- The client access checklist: what to ask for per duty, least-privilege scope, and what each connection unlocks
- Repos in scope with default branch, package manager, exact test command, review on or off, and protected dependencies
- The ticket pickup contract: trigger label, queue, daily cap, size ceiling, branch naming, off-limits areas
- Review standards: team conventions, correctness and security checklist, severity thresholds, never-comment paths, delivery mode
A report after each run
Sent to your Slack, Telegram, or another channel you connect.
Drafts that wait for you
Anything that leaves your business is written for your approval, not sent on its own.
Answers in chat
Ask it about its work any time from the agent's chat in your dashboard.
The AI Software Engineer, on autopilot
Each task runs on its own schedule in a managed environment. Adjust any of them, or add your own.
Task 01Weekly on Friday at 16:00
Weekly Client Report
Write the weekly engineering report. Read ~/workspace/BRAND.md (mode, reader, sign-off, tone), ~/workspace/OWNER.md, and this ISO week's ledger ~/ledger/YYYY-Www.md, plus the week's outputs in ~/reports/tickets/…
Once a week
Task 02Weekdays
Ticket Pickup Sweep
Follow your own draft PRs through review feedback and red CI, answer summons, check for a red default branch, then pick up newly tagged tickets. If no queue and no GitHub access are connected (gh auth status fails)…
About 5 runs a week
Task 03Weekdays
PR Review Sweep
Sweep the repos marked for review in ~/workspace/REPOS.md for open pull requests new or updated since ~/state/prs-seen.json, keyed by head SHA so a new push re-reviews and an unchanged PR never does…
About 5 runs a week
Task 04Daily
Error Triage Sweep
Check the configured error source (Sentry, else Datadog) for groups NEW or newly SPIKING since ~/state/errors-seen.json. If neither is configured, end silently. Dedup by fingerprint…
About 7 runs a week
Task 05Weekdays at 08:30
Daily Engineering Brief
Send the daily engineering brief, the one scheduled message of the day. Read the last 24 hours (since the previous brief; Monday covers the weekend) of ~/reports/tickets/, ~/reports/reviews/, ~/reports/errors/…
About 5 runs a week
Task 06Weekly on Monday at 06:30
Weekly Upgrade Sweep
Run the weekly dependency upgrade sweep. If GitHub is not connected (gh auth status fails) and no repo is cloned locally, end silently. For each repo in ~/workspace/REPOS.md…
Once a week
Task 07Weekdays at 07:00
Doc Drift Check
Run the docs drift check. Read ~/workspace/DOCS.md for where the docs live (a ~/kb/ import, the live docs site via crawl, or Notion if configured) and where changes ship from. If neither a change source…
About 5 runs a week
Task 08Daily
Critical CVE Watch
Hourly cheap check: look for newly published security advisories (GitHub advisory data; Snyk if configured) affecting a pinned dependency in a repo listed in ~/workspace/REPOS.md, new since ~/state/deps-seen.json…
About 7 runs a week
What it delivers
Each run ends with a message in your channel. Here is the brief the AI Software Engineer's first task works from.
AI Software EngineerAGENTWeekly on Friday at 16:00
Weekly Client Reportcompleted
The brief: Write the weekly engineering report. Read ~/workspace/BRAND.md (mode, reader, sign-off, tone), ~/workspace/OWNER.md, and this ISO week's ledger ~/ledger/YYYY-Www.md, plus the week's outputs in ~/reports/tickets/…
Deploy this template and Qoren provisions a dedicated, managed cloud environment: no Docker, VPS, or server upkeep. Tailor the persona, schedules, and tools, use the managed model key or bring your own, and the agent stays online with activity, usage, and spend in one dashboard.
How deployment worksSee pricing
Product names and logos are trademarks of their respective owners, shown here to indicate what this template connects to.
Sell the Software Engineer to your clients
Run one Software Engineer per client, each in its own isolated environment, and bill it as a monthly retainer.
- A sample week before the sale. Give it a prospect's website and it builds a sample week of its work from public information, ready to attach to your pitch.
- A weekly report under your name. It opens with the counts your client can check, written as your agency, and comes to you to forward.
- A client access checklist. Exactly which logins to ask the client for, and what each one unlocks.
- Hosting from $19 a month per client. A dedicated environment for one agent, plus model usage, which depends on volume. On the agency plans, each client's cost shows on its own line.
AI Software Engineer template questions
What does the AI Software Engineer template do?
The moment a PR opens it is reviewed; tagged issues become tested draft PRs, and review comments or red CI on its own PRs get fixed on the branch. Errors traced to a suspect line, upgrades drafted, a Friday client report. It runs 8 scheduled tasks on a managed cloud environment.
Which runtime does the AI Software Engineer use?
It runs on the Hermes runtime in a dedicated cloud environment that Qoren provisions and keeps online for you.
How often does the AI Software Engineer run?
On a schedule you control. Out of the box it runs weekly on friday at 16:00, weekdays, daily, weekdays at 08:30, weekly on monday at 06:30, weekdays at 07:00. You can change the cadence, or trigger it on demand. It also reacts the moment something happens: pr opened, issue labeled, linear issue tagged, error alert, vulnerability alert, push to default branch, pr feedback or mention, ci failed, once you connect those triggers.
Will the AI Software Engineer do things without my approval?
No. It drafts and prepares the work, and you stay in control of anything that leaves your business. A reply, an invoice reminder, or a public post is written for your approval, not sent on its own.
Can an agency resell the Software Engineer to its clients?
Yes. Deploy one Software Engineer per client, each in that client's own isolated environment with its own keys. It ships with a client access checklist and writes a weekly report under your agency's name, ready for you to forward. Nothing goes to your client without your approval.
Does the Software Engineer need every tool connected?
No. Each duty starts when its tool is connected and stays silent until then. Give it a website and it builds a sample week from public information alone, before you connect anything.
What do I need to connect before it works?
Start from the template and connect the tools it needs, then set a model key: use the managed key included with your plan, or bring your own on any plan. The AI Software Engineer runs on the Hermes runtime.
5 duties, one agent.
Each duty is also a specialist template that deploys on its own.
Explore use cases- Engineering
Ticket To PR
Tag a ticket and it's picked up, implemented on a branch, tested, and opened as a draft PR linked back to the issue. The work you'd hand a junior, done overnight and waiting for your review. It never merges, and it only touches work you've tagged.
Reacts toIssue labeledEvery 30 minutes on weekdays, 08:00 to 20:00+1 more
Works with GitHub, Linear, Jira, Slack.2 tasks - Engineering
Automated Code Review Agent
aka “PR Reviewer”
Every pull request reviewed within minutes of opening for correctness, security, and your team's conventions, with findings ranked and drafted for your call. It never approves, never merges.
Reacts toPR openedEvery 15 minutes on weekdays, 08:00 to 20:00+1 more
Works with GitHub, Linear, Jira, Sentry, Slack.2 tasks - Engineering
Incident Triage Agent
aka “Incident Triager”
New production errors triaged the moment they spike: grouped, blamed on the deploy that likely caused them, root-cause hypothesis and the suspect file:line attached, so you debug from a lead, not a wall of stack traces.
Reacts toError alertEvery 15 minutes+1 more
Works with Sentry, GitHub, Linear, Datadog, Slack.2 tasks - Engineering
Dependency Upgrade Agent
aka “Dependency Upgrader”
Outdated and vulnerable dependencies caught, the upgrade prepared and tested on a branch, the changelog risk spelled out. A draft PR you merge, never one that merges itself.
Reacts toSecurity alertWeekly on Monday at 06:00+2 more
Works with GitHub, Snyk, Linear, Slack.3 tasks - Support
Documentation Maintenance Agent
aka “Doc Keeper”
Keeps your docs honest. Diffs every shipped change against the documentation, flags the exact page that's now wrong, and drafts the fix into a queue you merge.
Reacts toCode pushedWeekdays at 06:00+1 more
Works with GitHub, Firecrawl, Notion, Google Drive, Slack.2 tasks
Deploy the AI Software Engineer today.
Sign in, start from this template, and go live in minutes. Plans from $39/mo.