> ## Documentation Index
> Fetch the complete documentation index at: https://yellowhammer.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand the Pulse and Inspector

> Use Pulse and Inspector to navigate Project activity and inspect records.

Yellowhammer's Pulse shows the selected [Project](https://yellowhammer.dev/docs/reference/statuses-and-glossary.md#project), and the Inspector explains the item you select. Use both to trace recorded activity and find the Linear issue or GitHub pull request where you take action.

## Read the Pulse

Select a Project in the sidebar. Its name and repository count head the Pulse. The groups appear in this order:

| Group | What it shows |
| - | - |
| **Needs you** | Blocked and Waiting on You Cards, authoring decisions, and returned Features requiring attention. |
| **Now** | Current Act and running Attempts, when recorded. |
| **Feature** | The in-flight Feature, its Repo Lanes, and the unmerged Features awaiting human review. |
| **Tonight / last Night** | The Night's verdict, state, disposition counts, outstanding failure notices, and link to its account. Before a Night exists, it shows the upcoming schedule where available. |
| **Health** | Diagnostic flags and relevant setup or repair actions. |

A Project's Pulse uses its own Journal. Selecting another Project changes the context; counts do not combine different Projects' Nights. An unknown field means the recorded snapshot does not supply it, rather than an inferred success.

## Inspect a Card, Feature, or Attempt

Select a Card in **Needs you** to open its Inspector. The header shows its state and Block Reason or waiting reason. **Details** identifies the repository, work kind, budget epoch, and Attempt and Round counts. **Routes** shows tried and excluded routes.

Expand an entry under **Attempts** to read its route source, start and end, classification, Rounds, and recorded Check results. The latest Attempt starts expanded. A Check can show its exit status and recorded output; a review Round can show requested changes. **View Prompts** opens captured prompts for the Attempt when available.

A Feature selection shows Repo Lanes, Card counts, pull request links, and recorded Verification. A Feature awaiting merge shows which repositories have reached mainline, its Feature Branches, and any **Stacked on** predecessor.

A running Attempt shows its Repo, Route, Round, start time, running duration, and recorded status. This status is not an agent terminal transcript. Where available, **Abort Attempt** asks you to confirm before triggering the engine command; it does not answer or re-ready the Card.

## Trace a Night's account

In **Tonight / last Night**, choose **Show the Night’s account**. The main area replaces the Pulse with the Night's recorded Journal events, and the Inspector shows its facts and link to Linear.

Move the playhead, step **Back 5 minutes** or **Forward 5 minutes**, or jump to **Previous problem** and **Next problem**. Selecting an outstanding failure notice opens the account at that failure. These are recorded events, not live agent output; the playhead moves when you move it. Use **Pulse** in the toolbar to return.

## Take action in the right place

Use **Open … in Linear** to answer a question, edit a Card, move it to Todo, or make Feature triage decisions. Open a pull request link to review or merge in GitHub. The app exposes engine controls and diagnostics, but its record views do not replace the board.

## Next steps

[Answer questions and unblock work](https://yellowhammer.dev/docs/review/answer-questions-and-unblock-work.md) · [Related reference](https://yellowhammer.dev/docs/reference/statuses-and-glossary.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.