Skip to content

Conversation

@julia-g-rose
Copy link
Contributor

@julia-g-rose julia-g-rose commented Dec 5, 2025

Add demo and repo people can clone. Goal:

  • Bring in joint users across all three platforms (Weave, Models, OpenPipe)
  • Gauge interest in Copilot analysis
  • Provide a clone-able repo to get started, which includes tricks like resuming crashed runs and integrating Weave scorers into the training loop

See Loom with project overview: https://www.loom.com/share/7ae454b4068f4a4390bfcf3d7ea82ffc

Add demo and repo people can clone. Goal:
- Bring in joint users across all three platforms (Weave, Models, OpenPipe)
- Gauge interest in Copilot analysis
- Provide a clone-able repo to get started, which includes tricks like resuming crashed runs and integrating Weave scorers into the training loop
@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2025

📚 Mintlify Preview Links

🔗 View Full Preview

📝 Changed (1 total)

📄 Pages (1)

File Preview
training.mdx Training

🤖 Generated automatically when Mintlify deployment succeeds
📍 Deployment: ac53673 at 2025-12-09 17:16:12 UTC

training.mdx Outdated

To get started, satisfy the [prerequisites](/training/prerequisites) to start using the service and then see [OpenPipe's Serverless RL quickstart](https://art.openpipe.ai/getting-started/quick-start) to learn how to post-train your models.

We also recommend checking out this public [demo workspace](https://wandb.ai/wandb/demo-project-qwen-email-agent-with-art-weave-models/workspace?nw=nwuserjuliarose) and [repo](https://github.com/julia-g-rose/openpipe-ruler-wandb-demo) that shows how to:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably should have one CTA - and sending to the workspace isn't that helpful

Suggested change
We also recommend checking out this public [demo workspace](https://wandb.ai/wandb/demo-project-qwen-email-agent-with-art-weave-models/workspace?nw=nwuserjuliarose) and [repo](https://github.com/julia-g-rose/openpipe-ruler-wandb-demo) that shows how to:
We also recommend checking out this [repo](https://github.com/julia-g-rose/openpipe-ruler-wandb-demo) that shows how to:

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 on CTA. On sharing the workspace, I think a demo workspace helps people see what a full integration looks like in the platform, prior to investing time into a project. Cloning a repo, running training, etc. is a big time commitment that is easier to justify if you know what the final integration will look like

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@scottire just updated to include a single CTA, but used the workspace (instead of the repo) so users can see the benefit of using W&B. The workspace includes a link to the repo in the project summary at the top.

* Train a Qwen model with OpenPipe RULER and [Weave Scorers](https://docs.wandb.ai/weave/guides/evaluation/scorers#create-your-own-scorers)
* Track training progress and [create custom plots](https://docs.wandb.ai/models/app/features/custom-charts) with W&B Models
* Evaluate the final results on a [Weave leaderboard](https://docs.wandb.ai/weave/cookbooks/leaderboard_quickstart#leaderboard-quickstart)
* Use AI to analyze your traces, loss curves and experiment results
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where does it use AI to analyze the traces?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The AI analysis was done ad hoc with Cursor and shared in the workspace demo, so it's not part of the code base. Included it to start seeing if there is interest in offering this sort of analysis within Workspaces out-of-the-box (instead of my current method of sharing traces and charts with Cursor via prompting). I recognize the statement is somewhat misleading, so can remove, but I think it will get us feedback around the direction

Screenshot 2025-12-05 at 9 10 10 AM

Copy link

@danielbolus danielbolus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me!

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.

4 participants