# Features

JARVIS is one assistant with several capabilities. Each of them is documented on its own page.

| Feature | What it does | Guide |
| --- | --- | --- |
| AI Assistant | Answers questions, follows context, uses its tools when a reply needs them | [AI Assistant](/jarvis/features/assistant/) |
| Web Search | Looks up current information and answers with sources | [Web Search](/jarvis/features/web-search/) |
| Conversations | Saved, searchable threads you can continue | [Conversations](/jarvis/features/conversations/) |
| Memory | Information that survives across conversations | [Memory](/jarvis/features/memory/) |
| Tasks | A task list you can drive from chat or the page | [Tasks](/jarvis/features/tasks/) |

## How they work together

The capabilities are not separate modes. In one conversation JARVIS can answer from what it
already knows, search the web because the answer needed to be current, and add an item to your
task list because you asked it to.

A typical exchange:

```text
You: What's the latest Node.js version? Search this on Google.
JARVIS: answers with the current version, plus a source list

You: Add a task to check the release notes for breaking changes.
JARVIS: "Added — 'Check the Node.js release notes for breaking changes' is on your list."

You: Which one is most important?
JARVIS: answers against the search results from earlier in this conversation
```

## Not available yet

These are visible in the interface but are not connected in the current release:

- File attachments from the composer
- Voice input
- Automations

JARVIS says so plainly when you ask for something in these areas rather than failing quietly.

## Related

- [Getting Started](/jarvis/getting-started/) — set up an account and start using JARVIS
- [Settings](/jarvis/account/settings/) — control memory, language, theme, and connections
- [API Overview](/jarvis/api/) — the same capabilities over HTTP