Repository navigation
Can I merge the updated pure Rust part into main branch code? #3266
Description
Activity
Id like you verify and merge it.
If you have improvements you'd like to contribute, the best approach would be to open a pull request from your fork (huagusam/claw-code) targeting ultraworkers:main. That way maintainers can review the diff, run CI, and merge properly. An issue alone doesn't give visibility into the actual code changes.
@huagusam please open a PR from your fork with the specific Rust changes. The maintainers can then review and merge if the changes are clean and pass CI. A direct merge request is easier to evaluate than asking in an issue.
Go for it — PRs are always welcome. Just make sure your changes stay within the Rust-only parts and pass cargo clippy and cargo test. If you need guidance on where to start, the src/ directory is well organized by module.
One additional consideration: if the pure Rust part introduces breaking API changes or changes to the CLI interface, those should land in a feature branch with a migration guide before merging to main. Otherwise, as long as the existing test suite passes with the Rust-native implementation alongside the current one, a phased rollout (feature-flag gated) would minimize risk.
https://github.com/huagusam/claw-code It is very powerful and memory save and token save
。