Development Guide
English | 中文
Frontend Dev Mode (Disk-First Assets)
The collector binary embeds frontend assets via RustEmbed at compile time. By default, every frontend change requires recompiling the collector (cargo build --release) to take effect.
To speed up frontend development, set the AGENTSIGHT_FRONTEND_DIST environment variable to serve assets directly from disk. This way you only need to rebuild the frontend and restart the collector — no Rust recompilation needed.
Usage
# 1. Build the frontend
make build-frontend
# 2. Start the collector with disk-based frontend assets
AGENTSIGHT_FRONTEND_DIST=./frontend/dist sudo -E ./target/release/agentsight record -c claude --binary-path <path>After each frontend change:
make build-frontend
# Restart the collector — changes take effect immediately, no cargo build neededHow it works
- On startup, the collector checks for the
AGENTSIGHT_FRONTEND_DISTenvironment variable. - Set — serves files directly from the specified directory, skipping the embedded asset extraction. The directory must contain
index.html. - Not set — falls back to the default behavior: extracts
RustEmbedassets to a temp directory and cleans up on exit.
Notes
- Use
sudo -Eto preserve the environment variable when running with sudo. - The path can be relative (e.g.,
./frontend/dist) or absolute. - In production, do not set this variable — the embedded assets will be used as usual.
Continue exploring
Back to index
AgentSight: System-wide AI agent tracing and monitoring with eBPF
  
Previous
Build From Source
Use this guide when developing AgentSight or building a local binary from the repository. If you only want to run a release binary, see the Quick Start in README.md.
Next
Docker Usage
Use Docker when you want a packaged AgentSight runtime for container, CI, or isolated Linux environments.
- Last updated
- Jun 3, 2026
- First published
- Jun 3, 2026
- Contributors
- LinuxDev9002
Was this page helpful?