> For the complete documentation index, see [llms.txt](https://docs.officepassword.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.officepassword.kr/using-browser-extentions/how-to-use-master-password-in-extension/master-password-upon-restarting-chrome.md).

# 크롬 재실행 시 마스터 비밀번호

Chrome 브라우저를 완전히 종료한 후 다시 실행하면 이전에 메모리에 유지되던 마스터 비밀번호가 존재하지 않습니다.

따라서 OfficePassword의 저장된 패스워드 정보를 사용하려면 **마스터 비밀번호를 다시 입력하여 잠금을 해제**해야 합니다.

동작 흐름은 다음과 같습니다.

1. Chrome 브라우저를 완전히 종료합니다.
2. Chrome을 다시 실행합니다.
3. OfficePassword 확장 프로그램을 엽니다.
4. 마스터 비밀번호를 입력합니다.
5. 인증이 완료되면 저장된 패스워드와 자동 입력 기능을 다시 사용할 수 있습니다.

이 방식은 사용자의 마스터 비밀번호가 로컬 저장 장치에 지속적으로 남지 않도록 하여 보안을 강화합니다.


---

# 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.officepassword.kr/using-browser-extentions/how-to-use-master-password-in-extension/master-password-upon-restarting-chrome.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.
