Provider abstraction
Choose the right provider for the job. A provider abstraction is intended to keep app experiences from being tied to one model vendor.
SHARED AI PLATFORM
One core. Many ways to build.
The best ecosystem feels connected without giving up control. JT AI Core is the planned shared intelligence layer for JT apps—designed to keep AI provider choices, model configuration, tool access, and privacy rules consistent while allowing each app to use only the capabilities it needs.
✳
PROVIDERSJeff AI · Cloud · Local
JT INTELLIGENCEContext-aware assistance
WORKSPACEFocused · Modular · Connected
STATUSEarly access concept
Made for the way you create.
The best ecosystem feels connected without giving up control. JT AI Core is the planned shared intelligence layer for JT apps—designed to keep AI provider choices, model configuration, tool access, and privacy rules consistent while allowing each app to use only the capabilities it needs. The JT ecosystem is designed to connect products while keeping each workspace focused on its own job.
Model and endpoint configuration
Keep configuration understandable. Model, endpoint, and connection settings should be explicit rather than hidden in application code.
App-scoped tool permissions
Give each app only the tools it needs. App-scoped permissions are intended to limit unnecessary access and make consent easier to review.
Privacy and diagnostics controls
Make privacy and diagnostics visible. Connection status, errors, and usage-related controls should help users understand what is happening.
A clearer path from idea to outcome.
Power a more connected JT. The interface is designed to make your next step easier to see, your decisions easier to revisit, and your work easier to organise.
PROVIDERS
Jeff AI · Cloud · Local
Provider abstraction is intended to give JT apps a consistent way to request AI capabilities.
APP PERMISSIONS
Tools · Access · Confirmations
Model and endpoint settings should be configurable without exposing private keys in browser code.
DIAGNOSTICS
Connection · Latency · Errors
Permission scopes and confirmation rules are intended to help keep tool access appropriate to each app.