osFoundry / Platform
Connections
See which integrations are live, their auth state and last sync.
What it is
Connections is the status view in osFoundry's Data & Memory area that shows, in one place, every integration you've wired into your workspace. Instead of hunting through separate settings screens to find out whether a source is actually working, you get one list: which integrations are live, what authentication state each one is in, and when each last synced. It answers the questions you actually ask when something looks stale — "is this still connected, or did the token expire?" and "when did I last pull data from it?"
Because osFoundry is a bring-your-own-key desktop workspace, the connections you see here are yours: they run against your own API keys and credentials, and the connection state lives with your local-first workspace rather than on a vendor's server. Each row surfaces the auth state — connected, needs re-authentication, or errored — so an expired credential shows up as a clear signal instead of silently failing in the background. The last-sync timestamp tells you how fresh the data behind your chats, agents, apps, and knowledge really is, which matters when an agent's answer depends on a source that hasn't refreshed in days.
The value is trust and speed. When you're relying on connected data to answer questions or run agents, you need to know the plumbing is sound before you act on the output. Connections turns "I think that source is connected" into something you can verify at a glance, and points you straight at the one integration that needs a fresh login rather than making you audit all of them.
Key capabilities
- Lists every integration connected to your workspace in one status view, so you never guess whether a source is wired in
- Shows each connection's auth state — connected, needs re-authentication, or errored — so expired credentials surface instead of failing silently
- Displays the last-sync time per integration, telling you how fresh the underlying data actually is
- Runs on your own bring-your-own keys, so connection state reflects your credentials with no reseller layer in between
- Local-first: your list of connections and their state stays with your desktop workspace rather than a vendor account
Use cases
- Solo builder: opens Connections after an agent returns stale results and spots one integration flagged for re-authentication, fixing it in seconds instead of re-checking every source
- Data-focused analyst: checks the last-sync column before running a report so they know the numbers reflect a recent pull, not day-old data
- Privacy-conscious professional: reviews exactly which integrations are live and authenticated on their own machine, confirming nothing is connected that they didn't intend
Frequently asked questions
How do I tell if an integration's authentication has expired?
Each connection shows its auth state directly in the Connections view. An integration whose token or credential has expired appears with a needs-re-authentication state rather than staying quietly listed as working, so you can see which one to reconnect without testing them one by one.
What does the last-sync time actually tell me?
It's the timestamp of the most recent successful pull from that integration. Use it to judge how fresh the data behind your chats, agents, and knowledge is — a source that last synced days ago is a sign to refresh before relying on its output.
Where is my connection information stored?
osFoundry is a local-first BYOK desktop workspace, so your connections run against your own API keys and their state lives with your workspace on your device rather than in a reseller's cloud account. There's no per-seat fee and no markup layered on top of your keys.