Skip to content

feat(live): add live-poll tool and pending signals guidance#16

Open
chiplay wants to merge 2 commits intomainfrom
feature/live-poll-skill
Open

feat(live): add live-poll tool and pending signals guidance#16
chiplay wants to merge 2 commits intomainfrom
feature/live-poll-skill

Conversation

@chiplay
Copy link
Copy Markdown
Collaborator

@chiplay chiplay commented Apr 14, 2026

Summary

  • Add live-poll to the Signals section of the live tool catalog
  • Add Pending Signals section explaining how agents receive and respond to comments and control changes piggybacked on tool responses
  • Guidance for handling new_comment and control_change signals

Context

The FullStory lidar MCP server now piggybacks pending signals (new comments, control changes) on every live-* tool response. The live-poll tool provides a lightweight heartbeat for checking signals between actions. This skill update teaches agents how to use these capabilities.

Note: Requires changes to Subtext backend (mn)

chiplay and others added 2 commits April 13, 2026 20:01
- Add live-poll to the Signals section of the tool catalog
- Add Pending Signals section explaining how agents receive and
  respond to comments and control changes piggybacked on tool responses
- Guidance for handling new_comment and control_change signals

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…oration

New workflow skill that auto-triggers when agents make UI changes.
Sets up a Subtext live viewer session, shares the viewer URL,
polls for comments/signals during implementation, and captures
before/after screenshots for the PR.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

| Tool | Description |
|------|-------------|
| `live-poll` | Check for pending signals (new comments, control changes) without taking a screenshot. Lightweight heartbeat. |
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wonder if we should have a tool that just does this and stores them somewhere the agent can see? getting the agent to poll for these on it's own might be unpredictable. not really sure what's best here tbh since even a sideband poll requires something back to claude or requires claude to do something to look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants