osFoundry / Platform
Connector configs
Authoritative source for every connection — scopes, secrets, OAuth config.
What it is
Connector configs are the part of osFoundry Studio that defines and stores how your workspace connects to everything outside it — the APIs, tools, and services your agents and apps reach for. Each connector holds the full picture of one connection in a single authoritative record: its OAuth client configuration, the exact scopes that connection is allowed to use, the endpoints it talks to, and the secrets or tokens it authenticates with. Instead of the same credential being pasted into a chat here, an agent there, and an app somewhere else, one connector config becomes the one place that connection is defined, and everything in the workspace references it.
Because osFoundry is a bring-your-own-key, local-first desktop workspace, the secrets inside a connector config are your own keys and tokens, not something rented through a reseller — and they can stay on your device rather than sitting on someone else's server. When a connection needs OAuth, the connector config is where the client details and redirect are set up and where the granted scopes are recorded, so you can see precisely what access a connection has been given rather than guessing. When a token needs rotating or a scope needs tightening, you change it in the connector config once and every chat, agent, and app that uses that connection picks up the change.
That single-source design is the point. Connections tend to sprawl — different keys for the same service, forgotten tokens, unclear permissions — and a scattered setup is both a maintenance burden and a security risk. Keeping scopes, secrets, and OAuth config together in one connector record means you always have an accurate answer to "what is connected, with what access, using which credential," which is exactly the question that matters when you audit access, hand a workspace to a teammate, or revoke something in a hurry.
Key capabilities
- Define each external connection once as a connector config, then reference it from any chat, agent, or app in the workspace
- Store OAuth client configuration and record the exact scopes a connection has been granted
- Keep API keys, tokens, and secrets local-first on your device under a bring-your-own-key model — no reseller markup
- Rotate a token or tighten a scope in one place and have every consumer of that connection pick up the change
- See at a glance what is connected, with which credential, and what access each connection actually has
Use cases
- Solo builder: wires an agent to a third-party API by setting up one connector config with the right scopes, instead of pasting the key into every prompt
- Privacy-conscious team lead: keeps all workspace secrets on-device via connector configs and audits granted OAuth scopes before sharing access
- Automation maintainer: rotates an expiring token in a single connector config and every app and agent that depends on that connection keeps working
Frequently asked questions
Where are the secrets in a connector config actually stored?
osFoundry is a local-first desktop workspace, so connector secrets — your own API keys and tokens under the bring-your-own-key model — can stay on your device rather than on a hosted server. There is no reseller sitting between you and the service you are connecting to.
What does a connector config include besides the secret?
A connector config is the authoritative record for one connection: its OAuth client configuration, the specific scopes that connection has been granted, the endpoints it talks to, and the credential it authenticates with. Keeping them together is what lets you see exactly what access a connection has.
If I change a connection, do I have to update it everywhere it is used?
No. Because everything references the one connector config, updating a token or adjusting a scope there flows to every chat, agent, and app that uses that connection. That single source of truth is the reason connector configs exist rather than duplicating credentials per use.