sauer/claw-code
1
0
Fork 0
mirror of http://10.0.2.1:3031/sauer/claw-code.git synced 2026-06-30 12:47:05 +10:00
Code Issues Actions Packages Projects Releases Wiki Activity
83bbf5c7cb
claw-code/rust/docs/releases/0.1.0.md

52 lines
2.2 KiB
Markdown
Raw Normal View History

Present Claw Code as the current Rust product The release-prep docs still framed the workspace as a Rust variant, which understated the owner's current product position. This update rewrites the README title and positioning so Claw Code is presented as the current product surface, while keeping the legal framing clear: Claude Code inspired, implemented clean-room in Rust, and not a direct port or copy. The draft 0.1.0 release notes now mirror that language. Constraint: Docs must reflect the current owner positioning without introducing unsupported product claims Constraint: Legal framing must stay explicit that this is a clean-room Rust implementation, not a direct port or copy Rejected: Leave release notes unchanged | would keep product-positioning language inconsistent across release-facing docs Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep future release-facing docs aligned on product naming and clean-room positioning before tagging releases Tested: Reviewed README and docs/releases/0.1.0.md after edits; verified only intended docs files were staged Not-tested: cargo check and cargo test (docs-only pass; no code changes)
2026-04-02 02:46:27 +10:00
# Claw Code 0.1.0 release notes (draft)
Clarify the Rust 0.1.0 public release surface The workspace already reports version 0.1.0 and exposes a broad CLI, but the top-level README was outdated on installation, capabilities, and current release status. This pass rewrites the README around verified source-build flows and adds a draft 0.1.0 release-notes file so the branch is ready for a public-release prep review. Constraint: Release-prep pass must stay docs-only and avoid runtime behavior changes Constraint: Public docs should describe only verified commands, paths, and current distribution status Rejected: Add packaging automation in this pass | outside the requested release-facing docs scope Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep README and release notes aligned with cargo metadata, CLI help output, and CI coverage before tagging future releases Tested: Verified version/package metadata with cargo metadata; verified CLI help and command paths with cargo run --quiet --bin claw -- --help; verified CI coverage from .github/workflows/ci.yml Not-tested: cargo check and cargo test (docs-only pass; no code changes)
2026-04-02 02:15:31 +10:00
## Summary
Present Claw Code as the current Rust product The release-prep docs still framed the workspace as a Rust variant, which understated the owner's current product position. This update rewrites the README title and positioning so Claw Code is presented as the current product surface, while keeping the legal framing clear: Claude Code inspired, implemented clean-room in Rust, and not a direct port or copy. The draft 0.1.0 release notes now mirror that language. Constraint: Docs must reflect the current owner positioning without introducing unsupported product claims Constraint: Legal framing must stay explicit that this is a clean-room Rust implementation, not a direct port or copy Rejected: Leave release notes unchanged | would keep product-positioning language inconsistent across release-facing docs Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep future release-facing docs aligned on product naming and clean-room positioning before tagging releases Tested: Reviewed README and docs/releases/0.1.0.md after edits; verified only intended docs files were staged Not-tested: cargo check and cargo test (docs-only pass; no code changes)
2026-04-02 02:46:27 +10:00
Claw Code `0.1.0` is the first public release-prep milestone for the current Rust implementation. Claw Code is Claude Code inspired and built as a clean-room Rust implementation; it is not a direct port or copy. This release centers on a usable local CLI experience: interactive sessions, non-interactive prompts, workspace tools, configuration loading, sessions, plugins, and local agent/skill discovery.
Clarify the Rust 0.1.0 public release surface The workspace already reports version 0.1.0 and exposes a broad CLI, but the top-level README was outdated on installation, capabilities, and current release status. This pass rewrites the README around verified source-build flows and adds a draft 0.1.0 release-notes file so the branch is ready for a public-release prep review. Constraint: Release-prep pass must stay docs-only and avoid runtime behavior changes Constraint: Public docs should describe only verified commands, paths, and current distribution status Rejected: Add packaging automation in this pass | outside the requested release-facing docs scope Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep README and release notes aligned with cargo metadata, CLI help output, and CI coverage before tagging future releases Tested: Verified version/package metadata with cargo metadata; verified CLI help and command paths with cargo run --quiet --bin claw -- --help; verified CI coverage from .github/workflows/ci.yml Not-tested: cargo check and cargo test (docs-only pass; no code changes)
2026-04-02 02:15:31 +10:00
## Highlights
Present Claw Code as the current Rust product The release-prep docs still framed the workspace as a Rust variant, which understated the owner's current product position. This update rewrites the README title and positioning so Claw Code is presented as the current product surface, while keeping the legal framing clear: Claude Code inspired, implemented clean-room in Rust, and not a direct port or copy. The draft 0.1.0 release notes now mirror that language. Constraint: Docs must reflect the current owner positioning without introducing unsupported product claims Constraint: Legal framing must stay explicit that this is a clean-room Rust implementation, not a direct port or copy Rejected: Leave release notes unchanged | would keep product-positioning language inconsistent across release-facing docs Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep future release-facing docs aligned on product naming and clean-room positioning before tagging releases Tested: Reviewed README and docs/releases/0.1.0.md after edits; verified only intended docs files were staged Not-tested: cargo check and cargo test (docs-only pass; no code changes)
2026-04-02 02:46:27 +10:00
- Initial public `0.1.0` release candidate for Claw Code
- Safe-Rust implementation as the current primary product surface
Clarify the Rust 0.1.0 public release surface The workspace already reports version 0.1.0 and exposes a broad CLI, but the top-level README was outdated on installation, capabilities, and current release status. This pass rewrites the README around verified source-build flows and adds a draft 0.1.0 release-notes file so the branch is ready for a public-release prep review. Constraint: Release-prep pass must stay docs-only and avoid runtime behavior changes Constraint: Public docs should describe only verified commands, paths, and current distribution status Rejected: Add packaging automation in this pass | outside the requested release-facing docs scope Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep README and release notes aligned with cargo metadata, CLI help output, and CI coverage before tagging future releases Tested: Verified version/package metadata with cargo metadata; verified CLI help and command paths with cargo run --quiet --bin claw -- --help; verified CI coverage from .github/workflows/ci.yml Not-tested: cargo check and cargo test (docs-only pass; no code changes)
2026-04-02 02:15:31 +10:00
- `claw` CLI for interactive and one-shot coding-agent workflows
- Built-in workspace tools for shell, file operations, search, web fetch/search, todo tracking, and notebook updates
- Slash-command surface for status, compaction, config inspection, sessions, diff/export, and version info
- Local plugin, agent, and skill discovery/management surfaces
- OAuth login/logout plus model/provider selection
## Install and run
This release is currently intended for source builds:
```bash
cargo install --path crates/claw-cli --locked
# or
cargo build --release -p claw-cli
```
Run:
```bash
claw
claw prompt "summarize this repository"
```
## Known limitations
- Source-build distribution only; packaged release artifacts are not yet published
- CI currently covers Ubuntu and macOS release builds, checks, and tests
- Windows release readiness is not yet established
- Some integration coverage is opt-in because live provider credentials and network access are required
- Public interfaces may continue to evolve during the `0.x` release line
## Recommended release framing
Present Claw Code as the current Rust product The release-prep docs still framed the workspace as a Rust variant, which understated the owner's current product position. This update rewrites the README title and positioning so Claw Code is presented as the current product surface, while keeping the legal framing clear: Claude Code inspired, implemented clean-room in Rust, and not a direct port or copy. The draft 0.1.0 release notes now mirror that language. Constraint: Docs must reflect the current owner positioning without introducing unsupported product claims Constraint: Legal framing must stay explicit that this is a clean-room Rust implementation, not a direct port or copy Rejected: Leave release notes unchanged | would keep product-positioning language inconsistent across release-facing docs Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep future release-facing docs aligned on product naming and clean-room positioning before tagging releases Tested: Reviewed README and docs/releases/0.1.0.md after edits; verified only intended docs files were staged Not-tested: cargo check and cargo test (docs-only pass; no code changes)
2026-04-02 02:46:27 +10:00
Position `0.1.0` as the first public release of Claw Code in its current Rust implementation for early adopters who are comfortable building from source. The feature surface is broad enough for real usage, while packaging and release automation can continue to improve in later releases.
Clarify the Rust 0.1.0 public release surface The workspace already reports version 0.1.0 and exposes a broad CLI, but the top-level README was outdated on installation, capabilities, and current release status. This pass rewrites the README around verified source-build flows and adds a draft 0.1.0 release-notes file so the branch is ready for a public-release prep review. Constraint: Release-prep pass must stay docs-only and avoid runtime behavior changes Constraint: Public docs should describe only verified commands, paths, and current distribution status Rejected: Add packaging automation in this pass | outside the requested release-facing docs scope Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep README and release notes aligned with cargo metadata, CLI help output, and CI coverage before tagging future releases Tested: Verified version/package metadata with cargo metadata; verified CLI help and command paths with cargo run --quiet --bin claw -- --help; verified CI coverage from .github/workflows/ci.yml Not-tested: cargo check and cargo test (docs-only pass; no code changes)
2026-04-02 02:15:31 +10:00
## Verification used for this draft
- Workspace version verified from `Cargo.toml`
- `claw` binary/package path verified from `cargo metadata`
- CLI command surface verified from `cargo run --quiet --bin claw -- --help`
- CI coverage verified from `.github/workflows/ci.yml`
Reference in New Issue Copy Permalink