// Use when finding rt-claw definitions, call sites, subsystem ownership, build wiring, OSAL boundaries, or platform-specific implementations.
| name | rt-claw-code-explorer |
| description | Use when finding rt-claw definitions, call sites, subsystem ownership, build wiring, OSAL boundaries, or platform-specific implementations. |
| license | MIT |
Search from the repository root and identify the owning layer before editing. rt-claw is split between platform-independent logic, OSAL backends, platform BSPs, and vendor code.
rg or rg --files from the repository root.meson.build, meson_options.txt, and platform build files to confirm
compilation ownership.git log -- <path> when subsystem history matters.AGENTS.md and CLAUDE.md before changing architecture, build, or
commit behavior.docs/en/ and docs/zh/ when changing documented behavior.| Path | Purpose |
|---|---|
claw/ | Platform-independent core, services, shell, and Tool Use logic |
include/ | Public headers and OSAL-facing APIs |
osal/freertos/ | FreeRTOS OSAL implementation |
osal/rtthread/ | RT-Thread OSAL implementation |
osal/zephyr/ | Zephyr OSAL implementation |
osal/linux/ | Linux OSAL for native tests and tools |
drivers/ | Hardware drivers |
platform/ | Board support and native build integration |
scripts/ | Build, check, QEMU, OTA, and cross-file helpers |
tests/unit/ | Linux-native C unit tests |
tests/functional/ | QEMU and Linux functional tests |
vendor/ | Third-party submodules; do not modify |
claw/ must not include FreeRTOS, RT-Thread, Zephyr, ESP-IDF, or
other RTOS/vendor headers directly. Use claw_os.h and public project
abstractions.osal/<rtos>/.platform/<board>/.platform/common/<vendor>/.drivers/<subsystem>/<vendor>/ with public
headers under include/drivers/<subsystem>/<vendor>/.platform/ or osal/.vendor/ submodules.Use when adding CI coverage for a new rt-claw module, feature chain, endpoint backend, service integration, or regression.
Use when building rt-claw, choosing a platform target, running QEMU, flashing hardware, or debugging C/Meson/native build failures.
Use when analyzing rt-claw build logs, QEMU output, serial monitor logs, CI failures, network/API failures, or boot/runtime crashes.
Use when rt-claw behavior, APIs, configuration, build commands, platforms, or developer workflows change and documentation may need synchronization.
Use when adding a new rt-claw service, driver, tool, platform helper, platform port, or RTOS backend.
Use when reviewing rt-claw changes for OSAL boundary violations, RTOS coupling, platform leakage, driver layering, or portability risks.