fix: clear detached

Author: ankur-arch

content/200-orm/500-reference/200-prisma-cli-reference.mdx

@@ -846,7 +846,6 @@ The `dev` command starts a [local Prisma Postgres](/postgres/database/local-deve
 | `--db-port` (or `-P`) | No       | Port number the local Prisma Postgres database server will listen on.                                                                               | `51214` |
 | `--shadow-db-port`    | No       | Port number the shadow database server will listen on.                                                                                              | `51215` |
 | `--debug`             | No       | Enable debug logging.                                                                                                                               | `false` |
-| `--detach`            | No       | Create and start the instance in detached mode (running in the background). Useful for automated workflows and CI/CD pipelines.                    | `false` |
 
 ### Examples
 

content/250-postgres/300-database/550-local-development.mdx

@@ -88,16 +88,6 @@ npx prisma dev --name mydb1
 
 Whenever you pass the `--name mydb1` to `prisma dev`, the command will return the same connection string pointing to a local instance called `mydb1`.
 
-### Creating detached instances
-
-You can create and start new Prisma Postgres instances in detached mode (running in the background) using the `--detach` flag:
-
-```terminal
-npx prisma dev --name mydb --detach
-```
-
-This creates a new instance and immediately starts it in the background, similar to `docker run`. This is particularly useful for automated workflows and CI/CD pipelines where you need instances to run without interactive terminals.
-
 ## Starting existing Prisma Postgres instances in the background
 
 You can start existing Prisma Postgres instances in the background using: