T
trantor-org/starpulse
StarPulse: a live map of workflows, lifecycle machines and the agents moving through them
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"trantor-org-starpulse": {
"command": "uvx",
"args": ["starpulse"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"trantor-org-starpulse": {
"command": "uvx",
"args": ["starpulse"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio trantor-org-starpulse -- uvx starpulse
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 1 ★ · trantor-org/starpulse · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 从该仓库的 GitHub 页面直接读取 · 条目类型：开源项目
- 收录与活跃
- 收录于 2026-10-25 · 最近见到 2026-11-14 · 共见到 24 次 · 被 2 个来源列出
- 评分构成
- 综合分 203 · 1 ★ · 2 个来源 · repo
- 安装
uvx starpulse
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
uvx starpulse。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: 开源项目。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
trantor-org/starpulse；我们收录于 2026-10-25；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。StarPulse
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Every task, workflow run and agent in flight, on one live page.
Live demo ·
Configure ·
Sources ·
Agent CLI ·
Adapters ·
Consumers ·
Security ·
Compatibility ·
Development loop ·
Contributing
## What it is and why
I wanted to see where my agents were in their sessions and which skills they
were using. Then I watched a video that mapped agent actions onto state
machines, and I wanted to map the whole agent lifecycle and pair it with the
Dagu workflows I already run, so scripts and DAGs could take over manual AI
commands and cut the step count.
StarPulse is what I built. It shows tasks, workflow runs and agents on one live
page. It produces data and leaves what to do with that data to you. It is not
tied to one agent harness or one lifecycle: you define the states, and it draws
and records them.
## Quick start
sh
uvx starpulse init # writes starpulse.toml, board.yaml, .starpulse/board/ and .claude/settings.json (--harness, --dir)
export STARPULSETOKEN=$(openssl rand -hex 16)
uvx starpulse serve # then open http://localhost:8766
init scaffolds a board machine with its roles declared, a [[board.guards]] rule, a [scheduler] table, a producer
whose token is read from STARPULSETOKEN, and the Claude Code telemetry export settings; it refuses to overwrite an
existing file. The board starts empty, with the lanes the machine's states name, ready for uvx starpulse task create.
### Working with AI agents
An agent works the board through the starpulse CLI, every verb printing JSON (Agent CLI). uvx starpulse skills install --claude --codex copies the bundled skills into the project. For any other agent, add a section to AGENTS.md or CLAUDE.md:
md
## Tasks
This project tracks work on a StarPulse board. Run uvx starpulse help --agent for every verb, its
arguments and exit codes. Read the board with uvx starpulse board and open a task with
uvx starpulse task create " ".
### Working without AI agents
The same verbs work typed by hand, and New task on the Kanban adds a task from the page. Both write the same board.
## Views
| Kanban | Star Map | Workflow runs |
Reads tasks from its own Markdown board, Backlog.md or Jira; runs from Dagu, GitHub Actions or systemd; agents from Claude Code and Copilot.
## Status
Live demo ·
Configure ·
Sources ·
Agent CLI ·
Adapters ·
Consumers ·
Security ·
Compatibility ·
Development loop ·
Contributing
## What it is and why
I wanted to see where my agents were in their sessions and which skills they
were using. Then I watched a video that mapped agent actions onto state
machines, and I wanted to map the whole agent lifecycle and pair it with the
Dagu workflows I already run, so scripts and DAGs could take over manual AI
commands and cut the step count.
StarPulse is what I built. It shows tasks, workflow runs and agents on one live
page. It produces data and leaves what to do with that data to you. It is not
tied to one agent harness or one lifecycle: you define the states, and it draws
and records them.
## Quick start
sh
uvx starpulse init # writes starpulse.toml, board.yaml, .starpulse/board/ and .claude/settings.json (--harness, --dir)
export STARPULSETOKEN=$(openssl rand -hex 16)
uvx starpulse serve # then open http://localhost:8766
init scaffolds a board machine with its roles declared, a [[board.guards]] rule, a [scheduler] table, a producer
whose token is read from STARPULSETOKEN, and the Claude Code telemetry export settings; it refuses to overwrite an
existing file. The board starts empty, with the lanes the machine's states name, ready for uvx starpulse task create.
### Working with AI agents
An agent works the board through the starpulse CLI, every verb printing JSON (Agent CLI). uvx starpulse skills install --claude --codex copies the bundled skills into the project. For any other agent, add a section to AGENTS.md or CLAUDE.md:
md
## Tasks
This project tracks work on a StarPulse board. Run uvx starpulse help --agent for every verb, its
arguments and exit codes. Read the board with uvx starpulse board and open a task with
uvx starpulse task create " ".
### Working without AI agents
The same verbs work typed by hand, and New task on the Kanban adds a task from the page. Both write the same board.
## Views
| Kanban | Star Map | Workflow runs |
Reads tasks from its own Markdown board, Backlog.md or Jira; runs from Dagu, GitHub Actions or systemd; agents from Claude Code and Copilot.
## Status
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/trantor-org-starpulse/)
- 来源
- github · https://github.com/trantor-org/starpulse
- 按领域浏览
- 开源项目
- Traction
- 1 ★
- 收录来源
- 2 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。