Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions training.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,10 @@ W&B Training includes integration with:
* A fully-managed backend on [CoreWeave Cloud](https://docs.coreweave.com/docs/platform).

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) that includes the following examples:

* 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