weave-instrument
Weave instrumentation
Complete the login check before editing or initializing. If no valid login exists, send only that section's reply and stop.
After a valid login, inspect the application's dependencies, agent boundaries,
and existing OTel provider. Confirm entity/project and runtime credentials
before sending data; never read, print, or commit API keys. Read
trace fidelity before changing any instrumentation
path. Initialize once at startup with
weave.init("entity/project") in Python or await weave.init(...) in Node.
Check login first
Before editing code or initializing tracing, verify the existing W&B login for
the target deployment with a noninteractive, read-only identity request through
the configured SDK or connector. Use credentials in place; never print, copy,
or inspect secret values. Do not call login or tracing init as a login probe.