Build and test local changes to twoliter before releasing
Build twoliter from local source and configure kits to use the locally-built binary for testing changes before release.
Edit files in twoliter/twoliter/src/ or twoliter/twoliter/embedded/.
cd twoliter
cargo build --release
The binary will be at target/release/twoliter.
Override TWOLITER_DIR to point to your local build directory:
cd kits/bottlerocket-core-kit
make build TWOLITER_DIR=./twoliter/target/release
After making more changes:
# Rebuild twoliter
cd ./twoliter
cargo build --release
# Test again
cd kits/bottlerocket-core-kit
make build TWOLITER_DIR=./twoliter/target/release
Verify the local twoliter is being used by checking the path:
cd kits/bottlerocket-core-kit
make build TWOLITER_DIR=./twoliter/target/release 2>&1 | head -5
You should see your modified twoliter being invoked.
Changes not taking effect:
cargo build --release after making changesTWOLITER_DIR is correctls -lh ./twoliter/target/release/twoliterBuild errors in twoliter:
cargo check to see detailed error messagescargo clippy to catch common issuescargo test to verify tests passKit build fails with local twoliter:
--log-level debug by modifying the Makefile temporarily or using the twoliter binary directlyTo go back to using the released version, simply omit the TWOLITER_DIR override:
cd kits/bottlerocket-core-kit
make build
This uses the default tools/twoliter/twoliter from the released version.
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer