# Workflow for forking an environment

**URL:** <https://discourse.julialang.org/t/workflow-for-forking-an-environment/93660>\
**Category:** General Usage\
**Created:** [January 27, 2023, 8:38pm UTC](https://discourse.julialang.org/t/workflow-for-forking-an-environment/93660 "2023-01-27T20:38:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jar1](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@jar1](https://discourse.julialang.org/u/jar1)\
**Post date:** [January 27, 2023, 8:59pm UTC](https://discourse.julialang.org/t/workflow-for-forking-an-environment/93660/4 "2023-01-27T20:59:16Z")

</div>

Like this:

> [@First Pluto notebook launches are slower on Julia 1.9 beta 3](https://discourse.julialang.org/t/first-pluto-notebook-launches-are-slower-on-julia-1-9-beta-3/93429/88):
>
> One workflow that might be nice interactively is something like ] activate --copy which creates a new environment that copies the current Project.toml and Manifest.toml over. That way you don’t have to pay a precompilation price when doing one-off things, but your state is saved if you want to return to it (even if your main environment changes).

---

_[View the full topic](https://discourse.julialang.org/t/workflow-for-forking-an-environment/93660)._