JARVIS UltraManualv1.31

Reference

Glossary

Access: what an agent may do with a connected app or MCP server: Read only, Changes need your approval or Full access. See The tools lock.

Agent: one AI teammate, with its own identity, memory, model and skills. Each agent is a Hermes profile.

Alert: a notification sent outside the dashboard, to a browser, a phone or Telegram.

Approval Inbox: what some messages and the rule form call the Decision queue.

Bell: the list of recent events in the top bar.

Board: the task board on Work > Board, with the columns To do, In progress, Review and Done.

Brief: what you tell the team about yourself, on Meet your team or Settings > General. Every agent keeps it in USER.md.

Composio: the service that holds your app sign-ins (Gmail, Slack, …) and makes app calls for your agents.

Context window: how much text a model can take in at once, in tokens.

Conversation: one chat thread with an agent or the whole team, and one Hermes session.

Decision queue: the list of requests waiting for your answer on Home.

Destination: where a rule sends its result: Approval Inbox, Docs, Telegram, To-do or Mission.

Docs: the document library on Work > Docs, kept as Markdown files under docs/.

Draft: something an agent wants to send or change, waiting for your approval.

Effort: how long a model thinks before answering. More effort is better on hard work, slower and costlier.

Fallback: a second model an agent switches to when its own model fails.

Handoff: what one mission step passes to the next.

Hermes: the agent program each agent runs in. JARVIS Ultra installs it and manages its profiles.

Job: a task one agent runs on a schedule. Its results land on the Board.

Local model: a model that runs on your computer through Ollama. Free; nothing leaves the machine.

MCP server: a service that offers tools to agents through the Model Context Protocol.

Mission: a goal the Orchestrator plans as steps for the team, with your approval of the plan and, optionally, of the result.

Needs you: the counter in the top bar: how many requests wait for your decision.

Orchestrator: the agent you talk to most. It plans missions and answers the whole team.

Paused: an agent switched out of work until you resume it.

Piper: the local voice engine, with eight voices that run on your computer.

Profile: an agent's folder in Hermes' home, holding its identity, memory, settings, keys and skills.

Provider: a company or server that runs models, such as Anthropic or OpenRouter.

Publish: for a skill, saving a checked version and giving it to agents. For remote access, making the dashboard reachable on your tailnet.

Quiet hours: a time window when alerts wait and arrive afterwards as one summary.

Retire: take an agent off the team. Its folder moves to profiles-archived/ and it can be restored.

Rule: something to watch for, an agent to act on it, and where its result goes.

Run: one execution of a job or a rule.

Service: the background program that keeps the dashboard running and brings it back after a restart.

Skill: a set of instructions an agent follows for a kind of task, kept as a SKILL.md folder.

Specialist: any agent other than the Orchestrator.

Step: one part of a mission, done by one agent.

Tailscale, tailnet: the private network service that lets your own devices reach the dashboard over https; your tailnet is the set of devices signed in to your Tailscale account.

Talk mode: speaking to an agent instead of typing, with replies read aloud.

Token: the unit models read and write text in; providers charge per million tokens.

Tool call: an agent's call to an app or MCP server. A Tool call card is a change the tools lock stopped for your approval.

Tools lock: the check in front of every agent's app and MCP calls that applies the access you set.

Turn: one run of an agent: reading what it is given, using tools, answering. Every turn is counted in Usage.

Whole team: a conversation the Orchestrator answers, handing parts to specialists.

XP: the Office score: 10 for each finished turn.