> For the complete documentation index, see [llms.txt](https://eirin-ai.gitbook.io/eirin-ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eirin-ai.gitbook.io/eirin-ai-docs/working-with-eirin/your-workspace.md). # Your workspace One page per agent for the replies waiting on you, the reports it has written, and a chat window to ask it anything. Each community manager has a **workspace**: the replies it needs you to look at, the reports it has written, and a chat panel beside them. Open it from the home page by clicking **Workspace** on the agent's card, or **Workspace** in the header of its profile. The header names the view and the game, for example "Replies · Supremacy: Call of War 1942", and offers three buttons: **Replies**, **Reports** and **Profile**. ## Replies The reply queue: **Needs you**, **Posted** and **Skipped**, each with a count. It holds store reviews from the App Store and Play Store alongside player comments from connected Discord and Instagram accounts, each card marked with its platform's icon. Approving, editing and skipping are covered in [Approve and post replies](/eirin-ai-docs/working-with-eirin/approve-and-post-replies.md). ## Reports Every report and follow-up the agent has written, newest first, with three columns: | Column | What it shows | | ------------- | -------------------------------------------------------------------------------------------------------------------------------- | | **Report** | The game name. Click the open icon to read the report. | | **Source** | Whether it is a report or a follow-up, and which platforms it drew on, for example "Report · Play Store, Reddit". | | **Generated** | Where the report came from (**Email** or **Web chat**) with a link to open the conversation behind it, and the date it was made. | ![The Reports view](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-76dca8a503706ef90f82a415f97ba5c6f67e6893%2F42_Workspace_reports.png?alt=media) ## Chat The panel on the right is the agent's web chat. It opens with three suggested prompts, such as "What's the current player sentiment across platforms?" and "Show me recent reviews mentioning bugs or crashes". Type your own question in **Ask {name} anything…** and press Enter. You can attach a file with the paperclip, or dictate with the microphone. ![A question answered from Play Store and Reddit data](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-1eb67444cc22d9e994b135bcbb37afcb1baf6c9d%2F43_Chat_question-answer.png?alt=media) {% hint style="info" %} **Questions are fast, reports take longer.** A search-style question ("show me reviews mentioning crashes") answers in under a minute. A full report analyses every connected source first, so expect a few minutes. The chat shows "Analyzing N sources…" while it works. {% endhint %} ### Ask for a report Type something like "Give me a report on player sentiment for the last 7 days". When it's ready, the chat shows a short summary with sentiment by source and a **View report** link that opens the full report as a PDF in a new tab. The report is also listed under **Reports**. ![A report summary in chat, with View report](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-fc6fff34cf00a664463ac23b03081fc59787654b%2F45_Chat_report-summary.png?alt=media) The PDF opens with a scorecard (sentiment score, positive and negative share, reviews analysed, primary risk), then an overview and numbered sections on what players said, what changed, and what to do about it. ![The first page of a report PDF](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-fccce3e06fb3176962fed5b181b98b304e167e1a%2F46_Report_pdf-page-1.png?alt=media) ### Conversation history Click the history icon in the top right of the chat panel to open **Sessions**. From there you can start a **New chat** or reopen any earlier conversation, grouped by Today, Previous 7 days and Older. Your conversations are private to you. ![The Sessions panel](https://592420414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGQPBrXn3FlQhSCpExATE%2Fuploads%2Fgit-blob-808a0da2d8c8613d7ff4634badff77d0114ee9f9%2F44_Chat_history.png?alt=media) ## Related pages * [Requests and reports](/eirin-ai-docs/working-with-eirin/requests-and-reports.md): everything you can ask * [Approve and post replies](/eirin-ai-docs/working-with-eirin/approve-and-post-replies.md) * [Chat, email and Slack](/eirin-ai-docs/working-with-eirin/chat-email-and-slack.md): the other ways to talk to Eirin --- # 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://eirin-ai.gitbook.io/eirin-ai-docs/working-with-eirin/your-workspace.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.