Get Started / Examples

Heddle Examples

Copy-paste examples for common local-first AI coding agent workflows: repository orientation, saved sessions, review, memory, browser oversight, heartbeat tasks, and visual debugging.

Summarize a repository

cd /path/to/project
heddle
# Prompt:
Summarize this repository, identify the main entrypoints, and list build/test commands.

A good first run asks Heddle to inspect the live project rather than relying on package names or assumptions.

Run a one-shot ask

heddle ask "List the main verification commands and explain what each one checks"

Ask mode exits after one prompt, but Heddle still saves the run as a session under .heddle/ for traces and later review.

Review the current Git diff

heddle
# Prompt:
Review the current git diff and tell me what should be verified before commit.

Heddle can combine Git-backed current review with trace-backed evidence from recent agent turns.

Teach a memory preference

Whenever I ask you to create a ticket, use these sections:
problem statement, proposed approach, considered alternatives, conclusion.

# Later:
Create a ticket for maintaining doc consistency after feature updates.

Durable preferences become memory candidates and can be folded into cataloged markdown notes for future sessions.

Open the browser control plane

heddle daemon
# Open the printed local URL, usually http://127.0.0.1:8765

Use the browser UI for saved sessions, current diffs, workspace switching, memory status, and heartbeat tasks.

Run a heartbeat task

heddle heartbeat start --every 30m --task "Check for safe repository maintenance work"
heddle heartbeat runs show latest

Heartbeat tasks are bounded recurring agent cycles with checkpoints, decisions, and saved run records.

Inspect a screenshot or diagram

heddle
# Prompt:
Look at /path/to/screenshot.png and explain the UI issue before editing code.

Terminal users can provide local image paths; browser uploads are saved as local paths for normal view_image behavior.