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

# nt3 status

> Check the current sync status of your translation files.

Display the current authentication status and project configuration for the CLI. Useful for debugging setup issues or confirming which credentials are active.

## Usage

```bash theme={null}
nt3 status
# alias: nt3 whoami
```

## Example output

```
nt3 CLI Status
================

Authentication:
  Source: global (~/.nt3/config.json)
  Token: entri_abc1...
  API URL: https://app.nt3.io (default)

Project:
  Project ID: proj_abc123
  Source language: en
  Config file: /Users/yourname/myproject/.nt3.yml
```

## What it shows

### Authentication section

Shows which token is currently active and where it came from. The CLI checks credential sources in priority order:

1. **Environment variable** — `NT3_API_TOKEN` is set in the current shell
2. **Local config** — `.nt3.local.json` exists in the current directory with a token
3. **Global config** — `~/.nt3/config.json` contains a token

If no token is found, the output is:

```
Authentication:
  Not authenticated
  Run "nt3 login" to authenticate (or "nt3 login --local" for folder-scoped)
```

The token value is always masked in the output (only the first 10 characters are shown).

If a local token is active and a global token also exists, `nt3 status` notes that the global token is present but not active for the current directory.

### Project section

Shows configuration read from `.nt3.yml` in the current directory:

* **Project ID** — the Entri project this directory is linked to
* **Source language** — the language your source strings are written in
* **Config file** — the absolute path to the `.nt3.yml` file

If no `.nt3.yml` is found:

```
Project:
  No .nt3.yml found
  Run "nt3 init" to initialize a project
```

## Options

`nt3 status` takes no flags.

## Use cases

* Confirm you are logged in before running `nt3 push` or `nt3 pull`
* Verify which project a directory is linked to
* Debug credential priority issues when using both local and global tokens
* Check which API URL is configured when using a self-hosted instance