CI Monitoring PRO

CI Monitoring is about filtering CI runs down to the ones that actually came from work on your machine.

Works with GitHub Actions and GitLab Pipelines. Bitbucket support is on the roadmap.

Built On Pro CI Actions

Triggering CI workflows is part of Devkeepr Pro more broadly. When Devkeepr detects a supported provider on a project, workflow actions can show up anywhere the app surfaces those project actions.

CI Monitoring builds on top of that. After you trigger a workflow or push changes from your machine, Devkeepr can keep the resulting runs in view without sending you back to your provider's dashboard.

Only See The Runs You Care About

The useful part is not just dispatching workflows. Devkeepr also knows when you push from your machine.

That means it can correlate your local Git activity with the workflow runs your provider starts afterward, and surface the runs that belong to what you are working on right now. Instead of a noisy feed of every run across every branch, you get the runs that were triggered by your own actions.

This is especially useful on busy repositories where multiple people are pushing all day. You can ignore unrelated CI noise and stay focused on your branch.

Cut Through Notification Noise

Because the relevant workflow runs are already visible in Devkeepr, you do not need provider notifications constantly pulling your attention away.

You can turn off the notification firehose and still keep a close eye on your own builds, checks, and deploy pipelines. Devkeepr surfaces the runs that matter to the project you are actively touching, so the signal stays high.

When one of your runs finishes, Devkeepr raises a single clickable notification that drops you on the run in the Process Window.

Where Runs Show Up

Workflow runs appear in a few places:

• Project detail panel for a project-scoped view of the runs tied to that repo
• Process Window for a unified view alongside local scripts and agents, grouped under each project
• Process Tray (optional, toggled in the app's Settings) for a compact panel pinned to the bottom-right of every main window view, showing active runs alongside your local processes

That means you can stay in the app while a workflow is queued, running, or failing, without context-switching back to your provider.

Drill Into Progress

Each workflow run includes live status updates, so you can quickly see whether it is queued, in progress, completed, or failed.

Expand a run to inspect its jobs and steps, see where it failed, and jump straight to the provider only when you actually need the full web view.

Turn A Red Build Into A Fix

On most dashboards a failed run is a dead end: you read the logs, then go fix it somewhere else. Devkeepr closes that loop. Hand a failed workflow or pipeline straight to an agent in one click, no copy-pasting logs or commit hashes.

• Fix with opens a fresh agent already briefed on the failure and able to pull the full run logs on its own.
• Fix in session drops the same failure into an agent you already have running on that project, so it keeps going with everything it already knows.

Which agents can do which is laid out in the Process Window docs.

See Process Window for more on how workflow runs are presented alongside your local work.