Epic: TinyClaw OpenClaw parity via Terraphim extensions
还没有人认领这个 Issue。
评估
调研方向
Start with docs/plans/tinyclaw-openclaw-parity-research-2026-02-27.md and docs/plans/tinyclaw-openclaw-parity-design-2026-02-27.md, then review the linked tracks #588, #589, #592, #593, and #591. Done means the listed parity tracks are implemented through existing Terraphim functionality, with practical core-channel workflows, consistent safety controls, and documentation matching shipped behavior.
由索引模型根据 Issue 内容生成。
描述
Summary
Track terraphim_tinyclaw capability parity with OpenClaw by extending Terraphim crates and shared patterns, not duplicating OpenClaw internals.
Principle (Non-Negotiable)
- Extend existing Terraphim functionality first.
- Do not introduce parallel/duplicate subsystems when a Terraphim crate or module already solves the problem.
Reference Docs
- Research:
docs/plans/tinyclaw-openclaw-parity-research-2026-02-27.md - Design:
docs/plans/tinyclaw-openclaw-parity-design-2026-02-27.md
Scope (Top 5 Tracks)
- #588 Foundation hardening (slash/session correctness, config wiring, unified guardrails)
- #589 Provider-backed web search/fetch quality
- #592 Markdown-defined commands and skills via shared Terraphim parsing/runtime
- #593 Voice transcription pipeline with graceful fallback
- #591 Orchestration extensions (session tools + spawn integration + cron sequencing)
Existing Related Issues (extend, don’t duplicate)
- #560 TinyClaw: Add agent spawning tool via terraphim_spawner
- #561 TinyClaw: Document standalone architecture
Exit Criteria
- TinyClaw users can achieve practical OpenClaw-like workflows on core channels.
- Markdown-defined commands/skills are first-class.
- Safety controls are consistent across tools and skills.
- Documentation matches shipped behavior.
- 主要语言
- Rust
- 星标
- 65
- 派生
- 5
- 平均合并
- 1 小时 17 分钟
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
terraphim/terraphim-ai 的其他 Issue
-
terraphim_rlm: require a per-sub-result verification plan (recheck / control / independent route)未关闭
难度 4/5 3-5 天 新手友好度 48/100
terraphim/terraphim-ai#969 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 35/100
terraphim/terraphim-ai#968 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 35/100
terraphim/terraphim-ai#967 ·
-
难度 4/5 3-5 天 新手友好度 48/100
terraphim/terraphim-ai#966 ·
-
难度 5/5 一周以上 新手友好度 30/100
terraphim/terraphim-ai#965 · 2 条评论 ·
查看 terraphim/terraphim-ai 的全部 Issue
相似的 Issue
-
area:docs documentation good first issue priority:low
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
triage:accepted
难度 2/5 1-3 小时 新手友好度 65/100
open-telemetry/otel-arrow#4343 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
mishraprafful/multihull#150 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 70/100
voidzero-dev/vite-plus#2970 ·
维护者通常 1 天内回复
-
ai_p2 comp-parquet-reader-v3
难度 2/5 半天 新手友好度 66/100
ClickHouse/ClickHouse#124986 ·
维护者通常 1 天内回复