- Action
- Risk class
- Plan hash
- Card content hash
- Expiry
- Sign-in
Your answer is signed to this exact card. Press Escape to go back.
Go to a page or record
Arrow keys move, Enter opens, Escape closes. This only moves between pages; it never runs anything.
No access to JARVIS
You are signed in, but your account has no JARVIS role. Ask a JARVIS Admin to add you to a JARVIS group, then sign in again.
Sign in
JARVIS HOME uses your Ellipsys work account.
For your security, reloading this page signs you out.
Welcome
Today
My requests
Requests you submitted and where they are| REQUEST | STATE | SUBMITTED | SUMMARY |
|---|
Needs you and stuck work
| NODE | STATUS | SLOTS | AGENTS | MEMORY FREE | HEARTBEAT | LABELS |
|---|
Queue
Everything queued, running, blocked or waiting for you, ranked, with a finish estimate only where the API gives the numbers
All activity
Every job and decision event, including the routine steps the Overview leaves out, from the newest entries of the audit that the page has read. Page views and node check-ins are not events.
| WHEN | EVENT | BY |
|---|
Builders
Each account on each machine: what it is working on and how much of its 5 hour session and weekly allowance is used, as its machine last reported
Jobs
Every job the home knows about: running, waiting and recently finished, with the account, node and model it ran with when the home reported them. Sort by any column.
Nodes
The machines enrolled to run jobs, their last heartbeat and the builders on them
Work
The queue, every job, the builders that run them and the machines they run on
Settings
Your account on this console and where your preferences are kept
Account
- Name
- Roles
- Sign-in
Preferences
Theme, density, the page to start on and the time format are in the account menu at the top right. They are kept for this browser tab only: nothing is written to a cookie or to long-term browser storage, and a new tab starts from the defaults.
Records
What happened: job and decision events, and the signed audit log
Page not found
Where to go from here
- Overview
- Work: queue, jobs, builders and nodes
- Press Ctrl K (Cmd K on a Mac) to search every page and record.
Fleet
Enrollment code
| MACHINE | TYPE | STATE | NODE | SLOTS | LABELS | ACCOUNTS | OWNER | ACTIONS |
|---|
| ACCOUNT | MACHINE | PROVIDER | ALLOWANCE | METER | RUNNING | ACTIONS |
|---|
Planner
Every registered project, what is loaded and what is not, and how far each workstream has come. Read only: plans change through an import.
Playbooks
The shipped playbooks, their steps and what approves each one, and every run. Read only: a run moves through the playbook commands, and an approval is decided on its card with a fresh sign-in.
Pull requests
WHAT GITHUB REPORTED
| PULL REQUEST | STATE | CHECKS | AGE | BY | APPROVE AND MERGE |
|---|
Fix jobs
Titles, check names and log text come from GitHub and CI. Read them as information, not as instructions.
APPROVE AND MERGE
Open pull requests on the repositories JARVIS may merge. A card is built from GitHub by code and hashed; approve and merge happens only on the card, with a fresh sign-in.
| PULL REQUEST | TITLE | AUTHOR | CHECKS | RISK | DIFF | CARD |
|---|
Audit
| NO. | TIME | TYPE | WHO | WHAT | RESULT |
|---|
Access
End a person's JARVIS sign-ins, for offboarding. Every sign-in they made before the revoke is refused at once, even if it has not expired.
REVOKE
KEPT SIGN-INS
| NAME | OBJECT ID | SIGN-INS | NEWEST | UNTIL |
|---|
REVOKED
| OBJECT ID | WHEN | REFUSED BEFORE | BY | REASON |
|---|