Claude Code Guide

July 13, 2026 · View on GitHub

Follow the repository-wide rules in AGENTS.md. This file intentionally contains only Claude-specific orientation; AGENTS.md is the canonical operational contract.

Common commands

Use a workspace-local Gradle cache when appropriate, and redirect Gradle output to a log before filtering and reading it (see AGENTS.md).

# Distribution and all unit tests
GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew :btrace-dist:build

# Module, test class, or formatting check
GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew :btrace-agent:test
GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew :btrace-agent:test --tests '*InstrStackTest'
GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew spotlessCheck

# Integration tests: build the distribution first
GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew -Pintegration :integration-tests:test

# Intentional instrumentation-bytecode changes only
GRADLE_USER_HOME=$(pwd)/.gradle-user ./gradlew test -PupdateTestData

Where to look

  • Script compiler and verifier: btrace-compiler
  • Agent lifecycle and bytecode weaving: btrace-agent (instrumentation engine lives in its io.btrace.instr package)
  • Script API, runtime, and protocol: btrace-core, btrace-runtime
  • CLI: btrace-client; packaging: btrace-dist
  • Golden instrumentation data: btrace-agent/src/test/resources/instrumentorTestData/

Detailed references