Which runtime does the Eng Pulse agent use?

It runs on hermes runtime in a dedicated cloud environment that Qoren provisions and keeps online for you.

How often does the Eng Pulse agent run?

On a schedule you control. Out of the box it runs weekly on friday at 15:00, weekly at 10:00, monthly on day 1 at 15:00. You can change the cadence, or trigger it on demand.

Will the Eng Pulse agent 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 I customize the template after deploying?

Yes. The template is a starting point: edit the persona, scheduled tasks, workspace, and connected tools to fit how you work.

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 Pro and above. The Eng Pulse agent runs on hermes.

Do I have to manage any servers?

No. Each agent runs in a dedicated, fully managed cloud environment. Qoren handles provisioning, isolation, runtime setup, and limits.

Eng Pulse Agent Template

What it does

The Eng Pulse agent, on autopilot.

Each task runs on its own schedule in a managed environment. Adjust any of them, or add your own.

Weekly on Friday at 15:00

Weekly Eng Pulse

Send the Friday engineering pulse covering the week, from every configured source per ~/workspace/DELIVERY.md (honoring its exclusions): delivery (PRs merged, cycle time, review latency, deploy frequency, reverts/hotfix…

task #01Weekly on Friday at 15:00

Weekly Eng Pulse

Send the Friday engineering pulse covering the week, from every configured source per ~/workspace/DELIVERY.md (honoring its exclusions): delivery (PRs merged, cycle time, review latency, deploy frequency, reverts/hotfix…

last run · completed

Weekly at 10:00

Blocked Radar

Check for work that is NEWLY stuck since ~/state/flow-seen.json (update it; exit fast when nothing changed): items blocked past the threshold in ~/workspace/DELIVERY.md, PRs waiting on review beyond the review SLA, a re…

task #02Weekly at 10:00

Blocked Radar

Check for work that is NEWLY stuck since ~/state/flow-seen.json (update it; exit fast when nothing changed): items blocked past the threshold in ~/workspace/DELIVERY.md, PRs waiting on review beyond the review SLA, a re…

last run · completed

Monthly on day 1 at 15:00

Monthly Eng Review

Compile the monthly engineering review for leadership: the month's trend lines from ~/state/pulse-history.json, DORA-style metrics flagged as directional rather than a scoreboard, and the top structural risk with one co…

task #03Monthly on day 1 at 15:00

Monthly Eng Review

Compile the monthly engineering review for leadership: the month's trend lines from ~/state/pulse-history.json, DORA-style metrics flagged as directional rather than a scoreboard, and the top structural risk with one co…

last run · completed

Example output

What it delivers.

A sample of what the Eng Pulse agent produces. Illustrative, with fictional data.

Example delivery

Example output

Weekly Eng Pulse · Weekly on Friday at 15:00

Send the Friday engineering pulse covering the week, from every configured source per ~/workspace/DELIVERY.md (honoring its exclusions): delivery (PRs merged, cycle time, review latency, deploy frequency, reverts/hotfix…

Delivered to your inbox, Slack, or Telegram.

Memory

Keeps its own workspace.

The agent maintains a persistent workspace between runs, so context carries forward instead of starting from scratch every time.

workspace

01Who the owner is — business, timezone, quiet hours, delivery channel
02What good looks like — targets, sources to include and exclude, the blocked threshold, what the owner optimizes for

Before & after

Stop running it by hand.

Doing it manually

Someone remembers to do the work, on time, every time
It stalls whenever a person is busy, asleep, or away
Context lives in someone's head instead of a workspace
Scaling it means more manual hours

With the Eng Pulse agent

The Eng Pulse agent runs the work on its own schedule
Stays online on a managed cloud environment, no server to run
Keeps its own workspace and context between runs
Tune the persona, schedules, and tools to your workflow

How it runs on Qoren

Live in three steps.

01

Deploy

Pick the template, get an environment

Start from this template and Qoren provisions a dedicated, managed cloud environment. No Docker, VPS setup, or runtime wrangling.

02

Configure

Tailor the persona, schedules, and tools

Adjust what the agent does and connect your tools. Use the managed model key included with your plan, or bring your own on Pro and above.

03

Stay online

Runs on schedules and triggers

The agent keeps working without a laptop or a server to babysit. Monitor activity, usage, and spend from one dashboard.

Eng Pulse template questions

Friday afternoon: what engineering shipped, what's stuck and why, and where the delivery risk is — one honest read of the team's week, pulled from the tools, not a status meeting. It runs 3 scheduled tasks on a managed cloud environment.

Deploy the Eng Pulse agent today.

Sign in, start from this template, and go live in minutes. Plans from $19/mo.

Deploy this template Browse all templates