> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/t4r/list-of-features/project-cleaner.md).
# Project Cleaner
Allows you to batch-remove selected unwanted elements from your projects
**Icon:** 
**Location:** ribbon Be.Smart T4R, panel Project
**Packages:** Be.Smart T4R
### **Overview**
The function Project Cleaner can batch-clear unwanted selected types of elements from your projects. In the command dialog, you can select the individual element types.
By using the command dialog, you have the flexibility to specify and select the individual element types that you wish to clear out. The elements this function can be applied to range widely, including Views, View Templates, Filters, Selection Filters, Drawings, Materials, Attached Files (x-refs), Imports, Images, Legends, Statements, Line Patterns, Groups, and Assemblies. This tool represents a significant enhancement over the original Line Pattern Deletion function, providing you with a more comprehensive and efficient project cleanup solution.
### Tutorial
{% file src="/files/eApuCsLfjw3SB1ZdNmou" %}
---
# 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.besmart.software/3d-modeling-and-design/t4r/list-of-features/project-cleaner.md?ask=&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.