DESIGN PARTNER
Build a clearer picture
of your coding agents.
Bring a real debugging or evaluation workflow. Help shape how RayTrace captures agent decisions, presents execution evidence, and makes experiments useful.
Prepare an inquiryA partnership around your workflow.
RayTrace is an early, open-source prototype. The design-partner conversation starts with a specific question your team struggles to answer about a coding agent.
What we can work on
- Setting up local trace capture for a compatible client.
- Understanding the gap between a proposed action and observed execution.
- Testing context changes with repeatable checks and baselines.
- Improving the dashboard around your debugging process.
What you bring
- A representative workflow and a concrete investigation question.
- Feedback on setup, inspection, and experiment results.
- A willingness to try early builds in a development environment.
- Sanitized examples you are comfortable discussing.
Start with one question.
“Did the agent actually run the command it reported?”
“Which context changes the action it takes next?”
“Does a fork improve the outcome on our check?”
We can use a small, reproducible task to define what to capture and what a useful result looks like. Scope, timing, and support are agreed during the conversation.
LET’S FIND THE USE CASE
Tell us what you are investigating.
Prepare a short introduction to the workflow you want to explore. Please leave out API keys, private prompts, and confidential repository content.
Early prototype. Clear expectations.
RayTrace is for local development, debugging, and evaluation. This is a collaborative product discussion, with no published trial terms, guaranteed outcomes, or production audit claims.
Read the evidence boundaries