Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

GJC compatibility campaign: Rust fork-in-spirit of gajae-code

未关闭
  • 哪里不对？
#3,319 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Yeachan-Heo 已经在做这个了。

开始于 2026年10月12日。

评估

这个 Issue 还没有评估数据。

描述

Objective

Make ultraworkers/claw-code a Rust fork-in-spirit of gajae-code (GJC), achieving SDK compatibility and capability compatibility.

Reference Implementation

Read-only: /home/bellman/Workspace/gajae-code (gajae-code SDK, tools, skills, settings)

Phase Overview

Phase 1: Foundation (SDK Wire Protocol)
  • WebSocket transport with frame correlation
  • Operation registry and error handling
  • Session routing and reconciliation
Phase 2: Core Capabilities
  • Complete 55-tool catalog (35/55 done, 20 gaps)
  • Skill discovery enhancement (bundled registry, chaining)
  • Task execution integration
Phase 3: Polish
  • Session-level settings override
  • 120+ slash commands (40/120+ done, 80 gaps)
  • Integration and optimization

Deliverables

  • Gap matrix analysis (docs/gjc-compat/gap-matrix.md)
  • SDK wire protocol implementation (new sdk crate, 4.5K LOC)
  • Session lifecycle SDK integration (2.5K LOC)
  • Tool catalog completion (3.5K LOC)
  • Skill system enhancement (1.4K LOC)
  • Slash command expansion (3.2K LOC)
  • Settings & configuration (0.5K LOC)
  • Integration tests and verification

Sub-Issues

See linked issues below for per-slice work.

Acceptance Criteria

  • All sub-issues closed with acceptance criteria met
  • SDK transport test passes with mock server
  • Session lifecycle operations work end-to-end
  • Tool execution matches GJC behavior
  • Skill discovery finds all scopes (bundled, project, user)
  • All AGENTS.md tests pass
  • Public docs contain no internal paths, hosts, or private infra

Related

Gap Matrix

— [repo owner's gaebal-gajae (clawdbot) 🦞]

主要语言
Rust
星标
195k
派生
108k
平均合并
1 天 9 小时
30 天内合并 PR
39

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。