> For the complete documentation index, see [llms.txt](https://docs.bluetext.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluetext.dev/getting-started-with-bluetext/how-to-work-with-bluetext/collaborating-with-bluetext.md). # Collaborating With Bluetext When using Bluetext in a team environment, we recommend starting by creating a basic app on one machine. Scaffold and implement the required services, then make this your initial commit. Once that’s done, other team members can clone the repository to begin contributing. You can then use Git to coordinate work—for example, one team member might handle the frontend while others focus on the database or API. To keep collaboration smooth, make small, frequent commits and regularly pull updates from the main branch. This minimizes merge conflicts and keeps changes easy to manage. A good practice is to pull the latest code and commit your updates after finishing a task or switching contexts in your coding agent. If you’re clearing your context, that’s also a great time to sync with the repository and resolve any conflicts. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bluetext.dev/getting-started-with-bluetext/how-to-work-with-bluetext/collaborating-with-bluetext.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.