---
name: essential-v2
version: 1.0.0
description: "Operate the Essential V2 shared pool inside Remote Dev full. Use for Essential V2 config selection, eager or day-2 activation, readiness, worker topology, UI organization selection, or shared-pool diagnosis."
metadata:
  requires:
    bins: ["cp9"]
  cliHelp: "cp9 cmd essential-v2.activate; cp9 cmd essential-v2.status"
---

# Essential V2

Read [`../get-started/SKILL.md`](../get-started/SKILL.md) for session routing and [`../get-started/references/safety-and-ownership.md`](../get-started/references/safety-and-ownership.md) before mutation.

Essential V2 is an optional shared-pool capability inside Remote Dev full. Copy [`../../cp9.dev-full.remote-ec2-k3d.example.yaml`](../../cp9.dev-full.remote-ec2-k3d.example.yaml); its `essential_v2` comments are the config source of truth.

## Activation And Readiness

1. Use `essential_v2.enabled: true` only when the pool must be part of `cp9 up` readiness.
2. Otherwise require top-level `cp9 status=ready`, run `bin/cp9 essential-v2 status config=cp9.yaml`, and activate with `bin/cp9 essential-v2 activate config=cp9.yaml` when needed.
3. Re-run status and require `ready`; eager and day-2 entry use the same idempotent bootstrap.
4. Switch the DBaaS UI to the alternate Essential V2 organization after activation. Starter/Essential v1 remains in the default organization.

Keep worker-topology changes explicit at initial activation. Do not infer Essential V2 product readiness from the Dev full baseline or from Premium resources.

## API And Images

Essential V2 shares Premium API semantics. Use [`../premium/references/operation-map.md`](../premium/references/operation-map.md) for operation lookup, after Essential V2 status is ready. Keep its observations separate from Premium.

Kernel images share the Premium nextgen catalog. Use [`../get-started/references/change-kernel-images.md`](../get-started/references/change-kernel-images.md) with the `SHARED_POOL` lane.

## Completion

Report Dev full readiness, Essential V2 activation/status, product behavior, and Session cleanup separately. Close the owned Session through `cp9 destroy`.

## References

- [`../premium/references/operation-map.md`](../premium/references/operation-map.md)
- [`../get-started/references/dev-full-aws-runtime.md`](../get-started/references/dev-full-aws-runtime.md)
- [`../get-started/references/change-kernel-images.md`](../get-started/references/change-kernel-images.md)