Skip to content

Add per-agent trace setup and isolated managed runs - #10

Merged
Stephen Belanger (Qard) merged 1 commit into
mainfrom
agent/per-agent-trace-setup
Aug 11, 2026
Merged

Add per-agent trace setup and isolated managed runs#10
Stephen Belanger (Qard) merged 1 commit into
mainfrom
agent/per-agent-trace-setup

Conversation

@Qard

Copy link
Copy Markdown
Collaborator

Summary

  • give Codex, Claude, OpenCode, and Pi independent persistent tracing settings files with one shared schema
  • add invocation-only settings for concurrent bt trace run processes without mutating or falling back to global agent configuration
  • add managed OpenCode and Pi launch support using their npm packages
  • route both real-agent integration harnesses through managed run
  • preserve structured destinations and profile/org selections in the JavaScript adapters

Validation

  • make test
  • cargo fmt --check --manifest-path bt-daemon/Cargo.toml
  • cargo test --manifest-path bt-daemon/Cargo.toml --all-features --locked
  • cargo clippy --manifest-path bt-daemon/Cargo.toml --all-features --all-targets --locked -- -D warnings
  • OpenCode installed-package integration scenario with mock inference and ingest
  • Pi managed-run integration scenario with mock inference and ingest

This PR is intentionally stacked on the Pi integration PR. The coordinated bt PR pins commit 952e2f26c8613d3fac82ca4999aae448a0b82139.

Base automatically changed from agent/pi-daemon-integration to main August 10, 2026 19:20
@Qard
Stephen Belanger (Qard) merged commit aa66906 into main Aug 11, 2026
20 checks passed
@Qard
Stephen Belanger (Qard) deleted the agent/per-agent-trace-setup branch August 11, 2026 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants