Skip to content

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

Open

Description

@Yeachan-Heo

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) 🦞]

Activity

  1. self-assigned this
    on Oct 12, 2026
  2. XinwangTao commented on Oct 13, 2026

    @XinwangTao

    Phase 1 is now effectively complete on the wire-protocol side: #3330 laid the frame/transport foundation, #3349 added reconnect/timeout/handshake/typed-error coverage, and #3351 delivered session lifecycle with reconciliation. That closes the first three checklist items; ready to move into Phase 2 tool-catalog completion.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions