> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/command-line-interface/reference/workbench/namespaces-get-active.md).

# namespaces get-active

Get the active namespace for the current user

## Synopsis

```shell
omics workbench namespaces get-active
  [--id]
```

## Description

Get the active namespace for the current user. The active namespace is the namespace currently being used for all workbench operations. By default, the command outputs the full namespace details as JSON. Use the `--id` flag to output only the namespace ID, which is useful for scripting and automation.

This command replaces the deprecated [namespaces get-default](/products/command-line-interface/reference/workbench/namespaces-get-default.md) command.

## Examples

Get the full active namespace details

```shell
omics workbench namespaces get-active
```

Get only the active namespace ID

```shell
omics workbench namespaces get-active --id
```

Use the active namespace ID in another command

```shell
omics workbench runs list -n $(omics workbench namespaces get-active --id)
```

## Flags:

### `--id`

Output only the namespace ID instead of the full namespace JSON. This is useful for piping the namespace ID into other commands or scripts.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.omics.ai/products/command-line-interface/reference/workbench/namespaces-get-active.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.