Back to corpus
research noteexperiment writeup candidatescore 24

Pulse Local Skill

Pulse runs autonomous development loops that iterate toward a goal without constant human intervention. This skill executes iterations locally via Claude Code subprocess, with iMessage notifications through Clawdbot.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

--- name: bot:pulse description: Manages Pulse autonomous development sessions with local execution via Claude Code homepage: https://github.com/diomandeee/comp-core user-invocable: true command-dispatch: pulse metadata.clawdbot: {"local_execution": true} manifest: inputs: [project_path, development_goal, max_iterations] outputs: [session_id, iteration_results, commit_hashes, completion_status] chains_with: [bot:dream-weaver, sys:plan, evo:evolve, tie:dist] triggers: [pulse, autonomous, develop, iterate, implement, execute] can_spawn_pulse: true --- Pulse runs autonomous development loops that iterate toward a goal without constant human intervention. This skill executes iterations locally via Claude Code subprocess, with iMessage notifications through Clawdbot. | Command | Description | |---------|-------------| | `/pulse @project "goal"` | Start an autonomous Pulse session | | `/pulse:status [id]` | Check session progress | | `/pulse:pause <id>` | Pause a running session | | `/pulse:resume <id>` | Resume a paused session | | `/pulse:abort <id>` | Stop a session | | `/pulse:list` | List recent sessions | | `/pulse:context <id>` | View full session context | 1. User defines a development goal 2. Pulse runs iterations autonomously (up to 10 by default) 3. Each iteration: analyze -> implement -> test -> commit -> signal 4. Signals determine flow: - `CONTINUE` - keep iterating toward goal - `COMPLETE` - goal achieved, session ends - `BLOCKED` - needs human input 5. User notified via iMessage after each iteration This will: 1. Resolve project path (Desktop/my-project or similar) 2. Create session in [home-path] 3. Start background loop runner 4. Execute iterations via `claude --print` subprocess 5. Send iMessage notifications on progress

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.