PyCharm 2026.1.1 introduces a major beta feature: native support for uv, Poetry, and Hatch workspaces. This Q&A explores how the IDE automatically detects workspace structures, manages dependencies, and configures environments to streamline multi-project Python development. Whether you're working in a monorepo or a multi-package setup, these changes reduce manual configuration and keep your projects in sync.

1. What are workspaces in Python project management, and why are they important?

Workspaces allow teams and organizations to manage multiple interdependent Python projects within a single repository. Instead of maintaining separate environments and dependency files for each service, a workspace lets you define shared packages, enforce version consistency, and simplify dependency resolution across all projects. This approach is especially valuable for large codebases where different services—like APIs, data processing scripts, and libraries—share common code. Using tools like uv, Poetry, or Hatch, developers can define a single pyproject.toml at the workspace root and let the tool automatically link sub‑projects. The result is less duplication, fewer conflicts, and a smoother development workflow.

2. What new workspace support does PyCharm 2026.1.1 introduce?

PyCharm 2026.1.1 adds built‑in, beta support for workspaces managed by uv, Poetry, and Hatch. This means the IDE can now automatically understand the structure of these workspaces directly from your pyproject.toml files. When you open a workspace, PyCharm scans the configuration, identifies individual projects and their interdependencies, and sets up an integrated environment without requiring you to manually import projects or specify SDK paths. Because this feature represents a fundamental shift in how PyCharm handles workspaces, it is opt‑in. You'll be prompted to enable it when opening a compatible project, or you can toggle it later in Settings | Project Structure.

3. How does PyCharm's intelligent workspace detection work?

When you open a workspace containing a pyproject.toml file from uv, Poetry, or Hatch, PyCharm parses the configuration to derive the entire project structure and all dependency relationships. This deep parsing eliminates the need for manual project imports or environment setups. The IDE recognizes which packages are part of the workspace, understands how they depend on each other, and presents a unified view. Because this detection relies on direct analysis of your configuration files, it is both accurate and low‑maintenance. The feature is currently in beta, so you may encounter edge cases, but it significantly reduces the time spent on project configuration when working with multi‑package setups.

4. How can I enable or configure workspace detection in PyCharm?

Workspace detection is opt‑in to ensure a smooth transition. When you open a project that uses uv, Poetry, or Hatch workspaces, PyCharm displays a dialog suggesting you enable automatic detection. You can accept this suggestion or decline for now. To manually manage the setting, navigate to Settings | Project Structure and toggle workspace detection on or off. A key note: if you previously hand‑edited .idea files to define projects, those custom settings may be overwritten when you agree to the new detection model. PyCharm will reset the configuration to match the pyproject.toml files, so make sure to back up any custom changes before enabling detection.

5. How does PyCharm visualize and manage dependencies across workspace projects?

After loading a workspace, you can inspect how projects relate to each other in Settings | Project Dependencies. PyCharm derives these dependency graphs directly from your pyproject.toml files and displays them as read‑only in the UI. This means you cannot edit the graph within the IDE—any changes must be made directly to the pyproject.toml files. Once you save your edits, PyCharm automatically updates its internal dependency model to reflect the new structure. This visual representation helps you quickly verify that your inter‑project references are correct and spot any unintended circular dependencies.

6. How does PyCharm handle automatic environment configuration for workspace projects?

PyCharm aims for a zero‑configuration approach to Python SDKs. When you open a .py or pyproject.toml file inside a workspace project, the IDE immediately checks whether a compatible environment already exists on your system. If it finds one (e.g., a previously created uv virtual environment), PyCharm automatically assigns it as the SDK for that project. If no compatible environment is detected, a file‑level notification appears suggesting that you create a new uv environment and install the necessary dependencies. This process is repeated for each project in the workspace, ensuring every sub‑project has its own correctly configured environment without manual intervention.

7. How does PyCharm maintain environment consistency over time?

Beyond the initial setup, PyCharm continuously monitors the health of each project's environment. It watches for changes in the pyproject.toml—such as added, removed, or version‑updated dependencies—and checks whether the environment remains in sync. If a discrepancy is detected (for example, a new dependency is not installed), PyCharm will alert you and offer to update the environment automatically. This ongoing surveillance prevents subtle bugs caused by forgotten updates or mismatched package versions across multiple services. The result is a development experience where your environments stay consistent with your defined requirements with minimal manual overhead.

8. What should I be aware of when transitioning to the new workspace support?

The new workspace feature is in Beta, so it may not cover every edge case. Before enabling detection, consider the following: (1) If you have manually customized .idea project files, those settings might be reset when you opt in. (2) The dependency graph is read‑only in the UI; all modifications must be done via pyproject.toml. (3) Only workspaces managed by uv, Poetry, or Hatch are supported—others may not benefit from the automatic detection. (4) For existing projects, you can always revert by disabling detection in Settings | Project Structure. Overall, the transition is designed to be non‑disruptive, but it's wise to review your current setup and back up any important configuration before switching.