Addresses
The following table maps each address you used before to its Forge equivalent.
Two details are worth remembering:
- The Weights & Biases app sits under
/wandb. A link that used to readwandb.ai/acme/my-projectis nowforge.coreweave.com/wandb/acme/my-project. Old links redirect, so bookmarks keep working. - Settings and your profile don’t sit under
/wandb. They sit at the top level offorge.coreweave.com, alongside the other Forge products. Team settings are the exception and stay with the app.
The top of the screen
The global header is new and belongs to Forge rather than to Weights & Biases. The following table maps each action you took in the old header to its Forge equivalent.Where alerts went
Alerts moved. You now configure them in three places:- User settings > Alerts, for your own run notifications
- Team settings > Team alerts, for a team’s Slack notifications
- Organization settings > Usage & Alerts, for usage and spending thresholds
What did not change
The following did not change:api.wandb.aistill works. Existing SDK scripts, CI jobs, and the mobile app keep running without changes. You don’t need to update theWANDB_BASE_URLenvironment variable.- Your credentials. Sign in with the same account you used before.
- Dedicated Cloud and Self-Managed. Forge is Multi-tenant Cloud only. If you use a
.wandb.ioinstance or run W&B yourself, your URLs, your sign-in page, and your product name are all unchanged.
Related
Forge Home
An overview of every product in CoreWeave Forge.
Get started with Weights & Biases
Follow a quickstart for experiment tracking or for tracing LLM applications with W&B Weave.
Forge and CoreWeave identity
For administrators: how the two identity systems relate, and where you manage each one.
Infrastructure and Forge billing
For administrators: which types of charges belong in which billing system, and where each billing task belongs.