> ## Documentation Index
> Fetch the complete documentation index at: https://resumecontext.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Machines

> Why every session records where it ran, and what your agent does with that.

Signing in with `resumecontext auth` binds **that machine**. Every session it
records carries that machine's identity, and every result your agent gets back
carries an `origin`:

| `origin`                    | Means                                                |
| --------------------------- | ---------------------------------------------------- |
| `this_machine`              | Recorded on the machine your agent is running on now |
| `same_person_other_machine` | Your own history, from another of your machines      |
| `other_person`              | A teammate's machine                                 |

## Why it matters

History is not proof that anything it describes exists here. A session from
another machine can reference files, checkouts, datasets, running services,
environment variables or credentials that are simply absent locally.

So when your agent reuses a command or path from a session that is not
`this_machine`, it is instructed to say where it came from and check the inputs
exist before running it.

<Warning>
  `origin` is the **only** evidence of which machine. Paths inside a transcript
  are just text that session recorded. Teammates commonly share a directory
  layout, and `/Users/<name>/work/repo` can exist on several machines or none.
  A familiar-looking path does not mean the work happened here.
</Warning>

## The web app

The dashboard shows `origin` per session too, but a browser is not a bound
machine, so your own sessions show as `unknown` there rather than claiming to be
`this_machine`.