---
question: How do I turn on the Code section in the Nexus dock?
kind: task
via_web: na
via_cli: available
via_python: na
via_api: na
via_config: available
ref_cli: abi new project --with-coding
ref_config: nexus_config.feature_flags
prereq: The coding stack (Coder, Forgejo, Actions) must be running. `--with-coding` on `abi new project` provisions it on the Docker stack only.
next:
  - /capabilities/platform/open-a-code-workspace
  - /capabilities/platform/code-workspaces
  - /capabilities/platform/business-workspaces
---

# Enable the Code dock

The Code dock section opens the editor and Forgejo repositories. It stays hidden until the workspace role policy includes the `code` feature and the coding stack is up. `abi new project` without `--with-coding` does not provision Coder or Forgejo, and the generated `config.yaml` for `abi dev up` keeps Code off even when you add the feature later.

## Web UI

Not applicable. There is no toggle in Nexus that provisions Coder or Forgejo. Create the project with `--with-coding`, or enable the feature in config and run the Docker stack, as on the Config tab.

## CLI

### Create the project with coding

When you scaffold the project, pass `--with-coding`:

```bash
abi new project my-app --with-coding
```

That writes the coding services into `config.local.yaml` for `abi stack start` and seeds Forgejo. It does not change the slimmer `config.yaml` used by `abi dev up`.

## Python

Not applicable.

## REST API

Not applicable.

## Config

### Enable the feature for roles

The `code` feature must appear in `nexus_config.feature_flags` for the roles that should see Code. On a `--with-coding` Docker stack, owners and admins get Code in the generated baseline; members and viewers do not. Adjust the matrix on [Organization settings](/capabilities/platform/organization-and-members).

Restart the API after editing feature flags.