> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/intro-en/update-note/2026/202609/2026.09.10.md).

# \[2026.09.10] Added component cutting editor and overhauled the My Projects page

## 1. Dashboard

### (Improvement) Revamped My Projects page

The My Projects page has been updated!

You can organize and view projects by folder. When creating a new project, just tell the AI what you want, and it will create it as is.

**Before**

<figure><img src="https://2613077494-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2FQUQzwJlkxzc8g7Krlsar%2Fimage.png?alt=media&amp;token=8d12c0f4-abf6-465d-bfeb-74d7def5f1b4" alt=""><figcaption></figcaption></figure>

**After**

<figure><img src="https://2613077494-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2FXCCMeuoAkVjH6cYSn2HK%2Fimage.png?alt=media&amp;token=c967b8da-0df8-459b-9ed8-9d1514498c98" alt=""><figcaption></figcaption></figure>

### Bug and issue improvements

* Fixed an issue where the 'Back to top' button did not work on mobile
* Cleaned up the parts where the UI and layout of the mobile consultation page were breaking
* Fixed an issue where you couldn't scroll with your finger on the mobile estimate screen

## 3. Parametric Editor

### (New) Added a part cutting editor

Added a cutting editor that automatically creates sheet (plywood) cutting plans based on components. View the parts list, sheet layout, required number of sheets, and cutting efficiency on one screen. If there are multiple layout candidates, it chooses one by considering material efficiency and actual workability.

If a panel is not rectangular, cutting dimensions are based on the outer rectangle that encloses the actual shape, and holes or grooves are separated as post-processing areas. Elements that are not cutting targets, such as hidden parts or 3D models, are excluded, and the reason they were excluded is also shown on screen.

The Outputs menu in the header was `Save / Export / Cutting`to `Save / Export`reduced to. When you click Export, options for printing drawings and cutting parts appear.

<figure><img src="https://2613077494-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2FiizTLXi9OZRte8gPl7pL%2Fimage.png?alt=media&amp;token=eccf7c70-8a5a-49e8-8637-55569915b7f4" alt=""><figcaption><p>When you click the Export button, you can choose the Print Drawings and Cut Parts buttons.</p></figcaption></figure>

When you click the Export button, you can choose the Print Drawings and Cut Parts buttons.

<figure><img src="https://2613077494-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2FLPortW3yEQvTQXCNFhU4%2Fimage.png?alt=media&amp;token=3ad1fcdc-6f3e-4459-bd81-ea41655bdca1" alt=""><figcaption><p>Cutting editor modal</p></figcaption></figure>

Cutting editor modal

### Bug and issue improvements

* Edit and save hidden conditions for enterprise parameters by component
* Even if the parameter edit form gets long, the Save/Cancel buttons stay pinned to the bottom
* Fixed an issue where the placement offset was not saved and was not reflected in the bounding box
* Values entered in MathInput remain even after saving and reopening


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archisketch.com/guide/intro-en/update-note/2026/202609/2026.09.10.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
