Skip to main content
Three connectors, on the Integrations page.

GitHub

Selected repositories feed team Knowledge; repos attach to projects for a read-through commit timeline.

Weights & Biases

Import local run directories or a hosted project, or keep a connection syncing.

Benchling

Notebook entries from selected Benchling projects.

​
Two controls per connection

Keeps new content flowing in as it appears upstream.
Live sync has a cutoff: it covers what is created after you turned it on. A run that already existed when you enabled it is history, and history is what backfill is for. Enabling sync and then starting a run is a test of live sync; attaching to a run that already finished is a test of backfill.
A bounded pass over what already exists.Enabling live sync on a Benchling connection queues a history pass automatically, so existing notebook entries appear without a separate verb.

​
Where imported content lands

Connecting W&B or Benchling asks for the workspace name, prefilled with the source and editable. The slug is derived for you — lowercased, hyphenated, and suffixed if taken.

​
Disconnecting

Disconnecting clears the stored content for that installation before releasing the claim, in that order — releasing first would strand the content with nothing able to clear it. A failure before the release leaves the integration connected and the disconnect retryable. Shared documents owned by a different installation, and unbound legacy documents, are preserved; the purge preview says so. There is never a source-wide purge fallback, and missing engine configuration is reported as an error rather than treated as proof of an empty index.

​
Importing without a connector

For folders of work, saved coding sessions and local W&B directories, the path is backfill — no connection required.