> 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/update-note/2026/202607/20260709.md).

# \[2026.07.09] 견적·Agent 기능 업데이트

### **1.1. (개선) 견적서 섹션 노출 및 순서 설정**

이제 견적서에 표시되는 **가구·마감재·기타 섹션의 노출 여부와 순서**를 기업별로 자유롭게 설정할 수 있습니다.

사용하지 않는 섹션은 숨기고, 필요한 섹션은 드래그하여 원하는 순서로 배치해 보세요.

설정한 내용은 해당 기업의 모든 견적서에 적용되며, 기본 순서는 **가구 → 마감재 → 기타**입니다. 단, 견적서 생성을 위해 **최소 1개 이상의 섹션은 반드시 노출되어야 합니다.‌**

이전

![](https://2510524506-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2Fgit-blob-92eb67a13881e4c505758f122f4f913c5816627e%2F202607_20260709-1.png?alt=media)

**이후**

![](https://2510524506-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2Fgit-blob-fa61c9cdd6908bccf911048eec939422e6810cbc%2F202607_20260709-2.png?alt=media)

### **1.2. (개선) Archisketch Agent 음성 대화 기능**

이제 Archisketch Agent와 **음성으로도 대화**할 수 있습니다.

음성으로 질문하면 Agent가 내용을 인식해 요청을 처리하고, 답변을 음성으로 안내합니다. 텍스트 입력 없이도 더욱 편리하고 자연스럽게 Agent를 이용해 보세요.

![](https://2510524506-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMWuDtKHjyUXqBIf7Q6Zw%2Fuploads%2Fgit-blob-8190631fa730e0e6fbd228d179a381f3cb489f15%2F202607_20260709-3.png?alt=media)


---

# 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/update-note/2026/202607/20260709.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.