Skip to content

refactor(rust): move implementation to rust/clawcode workspace - #3289

Open
huagusam wants to merge 6 commits into
ultraworkers:mainfrom
huagusam:restructure/rust-clawcode-workspace
Open

refactor(rust): move implementation to rust/clawcode workspace#3289
huagusam wants to merge 6 commits into
ultraworkers:mainfrom
huagusam:restructure/rust-clawcode-workspace

Conversation

@huagusam

Copy link
Copy Markdown

Restructures the Rust codebase into a self-contained \clawcode\ workspace under
ust/clawcode, collocating claw config (agents, skills) with the Rust crates.

  • Move crates: agents, api, claw-cli, commands, compat-harness, migrate-patch-names, mock-anthropic-service, plugin-types, plugins, runtime, telemetry, tools
  • Drop the old flat
    ust/\ crates tree
  • Add
    ust/clawcode/claw/\ workspace config with agents and skills
  • Gitignore local .env\ secrets (\claw/.env, \claw/.env_deepseek)

Verified: \cargo build --release\ succeeds in the new workspace.

Restructures the Rust codebase into a self-contained clawcode workspace
under rust/clawcode, collocating claw config (agents, skills) with the
Rust crates. Follows the project convention of keeping source under rust/.

- Move crates: agents, api, claw-cli, commands, compat-harness,
  migrate-patch-names, mock-anthropic-service, plugin-types, plugins,
  runtime, telemetry, tools
- Drop the old flat rust crates tree
- Add claw/ workspace config with agents and skills
- Gitignore local .env secrets (claw/.env, claw/.env_deepseek)
@1716775457damn

Copy link
Copy Markdown

This restructure looks good — collocating the claw config (agents/skills) with the Rust crates under rust/clawcode keeps configuration in sync with the code, and gitignoring the local .env secrets is the right call. Since cargo build --release passes in the new workspace, the move seems safe. Thanks for cleaning up the old flat crates tree too.

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