Build with Jarvis.
Give your product a personal AI foundation. Start with identity. Ask for context. Keep the user in control.
Start with your goal
Section titled “Start with your goal”Public docs. Private source. SDK packages and self-hosted repositories require explicit GitLab access. Understand access →
Choose your integration surface
Section titled “Choose your integration surface”Understand the boundary
Section titled “Understand the boundary”Jarvis is more than its terminal. External products use the application SDK to link an identity and request specific personal context. Your application owns its accounts and private product data; Jarvis owns the identity link, permissions and portable assertions. Signing in never silently shares those assertions.
See the contract
in motion.
A session opens the door.
Consent decides what crosses it.
{
"signed_in": false,
"personal_context": "not requested"
}Choose Sign in to begin. This is a local illustration, not a live account.
Available now, not promised later
Section titled “Available now, not promised later”| Available in this alpha | Not part of this release |
|---|---|
| Registration, sign-in and per-app identity | General-purpose agent orchestration SDK |
| Explicit personal-context consent and owner audit | Calendar, goals, fitness or investing scopes |
Four owner-entered fields for job_application |
Employer submissions or delegated actions |
Go and TypeScript 0.2.0-alpha.1 |
Python SDK or production certification |
Private distribution, public boundary. Repository and package reads require GitLab access. “Public SDK” describes the supported application interface, not anonymous access to packages or user data.
Looking for the desktop client instead? Get Jarvis for macOS.