> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/team-workspace/home.md). # Home Home is the first screen you see when you open your Riff workspace. It's your starting point — from here you can open any app or agent you've built, or start something new. ## What you'll find on Home **Your apps and agents** A grid of everything in your workspace. Each card shows the name, a short description, and when it was last updated. Click any card to open it. **Recent activity** A feed of what's been happening — agent runs completed, tasks raised, integrations triggered. Useful for a quick morning check without opening each app individually. **New App / New Agent buttons** The two primary actions in Riff. Use these to start building. If you're not sure which to pick, see [Apps and Agents](https://github.com/ElleNealAI/riff-docs/blob/main/concepts/apps-and-agents/README.md). ## Finding something specific If you have more than a handful of apps and agents, use the search bar at the top of Home to filter by name. You can also filter by type — Apps only, or Agents only. --- # 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.riff.ai/reference/team-workspace/home.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.