# AI use cases for Xyne Spaces (juspay/xyne-spaces) Repo: [juspay/xyne-spaces](https://github.com/juspay/xyne-spaces) | Use cases: 4 | Page: https://dedupedai.com/use-cases/juspay-xyne-spaces/ Xyne Spaces is an open source org OS in TypeScript that brings an organization's conversations, documents and tickets into one permission-aware context store, with collaborative apps and sandboxed agents built on top. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run the full Xyne Spaces stack on your machine: https://dedupedai.com/use-cases/juspay-xyne-spaces/run-xyne-spaces-locally/ - Triage incoming support tickets with Automations: https://dedupedai.com/use-cases/juspay-xyne-spaces/triage-support-tickets-with-automations/ - Have a Claw agent review a repository with approval gates: https://dedupedai.com/use-cases/juspay-xyne-spaces/review-a-repo-with-a-claw-agent/ - Let an agent act on GitHub through brokered MCP tools: https://dedupedai.com/use-cases/juspay-xyne-spaces/connect-github-tools-to-an-agent/ ## How to run the full Xyne Spaces stack on your machine with Xyne Spaces Repo: [juspay/xyne-spaces](https://github.com/juspay/xyne-spaces) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Clone the repo and start the dashboard, backend, Claw and Claw Auth with one command. **Who it is for:** A developer or platform engineer who wants to evaluate Xyne Spaces before connecting real org data. **The problem:** Setting up an org OS with several apps, databases and an agent plane by hand takes many steps and easy-to-miss configuration. **The outcome:** The dashboard, backend API, Xyne Claw and Claw Auth run on localhost and you can sign in with the local admin account. ### Steps 1. On macOS, install OrbStack with `brew install orbstack`, then start it with `open -a OrbStack`. 2. Clone the repo with `git clone https://github.com/juspay/xyne-spaces.git`. 3. Enter the folder with `cd xyne-spaces`. 4. Start everything with `pnpm run up` and answer the feature and app prompts. 5. Open http://localhost:5173 and sign in with admin@xyne.ai and xynelocal@123. ### Prompt to paste into your agent ```text Clone https://github.com/juspay/xyne-spaces.git into , run `pnpm run up` from the repo root, and report which phase failed if any. Expected output: the dashboard at http://localhost:5173 responds and the backend API at http://localhost:3001 responds. Verify both URLs return a page before reporting success. ``` ### Caveat The README says the local sign-in credentials are for local use, so change the setup before pointing the stack at real organization data. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/juspay-xyne-spaces/run-xyne-spaces-locally/ ## How to triage incoming support tickets with Automations with Xyne Spaces Repo: [juspay/xyne-spaces](https://github.com/juspay/xyne-spaces) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Let scheduled agent runs classify and triage Customer Support Desk tickets in the background. **Who it is for:** A support lead whose queue fills up faster than the team can sort it, and who wants routine triage done without someone remembering to run it. **The problem:** Incoming tickets sit unclassified, so urgent issues and SLA deadlines get missed. **The outcome:** New tickets arrive in the Customer Support Desk already classified and sorted into queues, with SLA deadlines tracked. ### Steps 1. Start the stack with `pnpm run up` and sign in at http://localhost:5173. 2. Open the Customer Support Desk and confirm ticket intake and queues are set up. 3. Open Automations and create a ticket triage and classification job. 4. Choose the queue or board the job should write to and set a schedule. 5. Review the first batch of classified tickets and adjust the instructions if the labels are wrong. ### Prompt to paste into your agent ```text Using the xyne-spaces repo at , set up a ticket triage and classification automation for the Customer Support Desk. Expected output: a list of tickets with a classification and queue for each. Verify that each ticket is classified only from ticket content the signed-in user can access. ``` ### Caveat The README describes triage and classification as Automations features but does not give the exact setup screens, so confirm the steps in the app before relying on them. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/juspay-xyne-spaces/triage-support-tickets-with-automations/ ## How to have a Claw agent review a repository with approval gates with Xyne Spaces Repo: [juspay/xyne-spaces](https://github.com/juspay/xyne-spaces) | Difficulty: Advanced | Time: 1 hour 30 minutes | Basis: From the README Run a sandboxed agent that reads a repo and runs code, with you approving every write. **Who it is for:** An engineering lead who wants an agent to read a codebase and report on it, without giving it write access by default. **The problem:** Code review and investigation take time, and agents that run code are risky when they can change things without a check. **The outcome:** The agent returns a review of the repository, and every write it proposes waits for your approve or decline click. ### Steps 1. Start the stack with `pnpm run up` and open http://localhost:3002 for Xyne Claw. 2. Create an agent in Claw and point it at the repository you want reviewed. 3. Ask the agent for a read-only review of the code and its failing tests. 4. When the agent proposes a write, such as a ticket or a message sent as you, approve or decline the card in the thread. 5. Read the final review and check the cited files before acting on it. ### Prompt to paste into your agent ```text Use the Claw agent in Xyne Spaces to review the repository that is connected to my account. Expected output: a short review listing issues by file and line. Verify that every write action waits for approval and that no write happens without a card being approved. ``` ### Caveat The README says the sandboxed shell runs in a Kata Containers microVM with egress closed, so the agent cannot reach outside networks from that shell, which limits what the review can fetch. Risk, remote script: Claw agents run real code and shell commands inside a sandbox, so review what the agent executes before approving any follow-up work. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/juspay-xyne-spaces/review-a-repo-with-a-claw-agent/ ## How to let an agent act on GitHub through brokered MCP tools with Xyne Spaces Repo: [juspay/xyne-spaces](https://github.com/juspay/xyne-spaces) | Difficulty: Advanced | Time: 1 hour 30 minutes | Basis: From the README Connect GitHub through Claw Auth so an agent can work with your repos under your own access. **Who it is for:** A developer who wants an agent to open or read GitHub items, and who needs that access tied to their own account. **The problem:** Giving an agent a shared token for GitHub would let it act with more access than the person asking. **The outcome:** The agent calls GitHub tools through Claw Auth using your own configured connection, and only for actions you are allowed to take. ### Steps 1. Start the stack with `pnpm run up` and sign in at http://localhost:5173. 2. Open the MCP tools settings for your user and connect GitHub. 3. Confirm Claw Auth at http://localhost:3003 shows the GitHub integration as available. 4. Ask a Claw agent to list open items in a repository you own. 5. Approve any write the agent proposes, such as opening an item, before it runs. ### Prompt to paste into your agent ```text In the xyne-spaces Claw setup, use the GitHub MCP tool through Claw Auth to list open issues in the repository . Expected output: a list of issue titles and numbers. Verify that the tool call came from your own connection and that the result matches what you see on GitHub. ``` ### Caveat The README lists GitHub among more than 50 brokered MCP integrations, but it does not document the exact GitHub setup screens, so check Claw Auth before assuming a given tool exists. Risk, credentials: The GitHub connection is tied to your own account, so a shared or leaked token would give an agent your repository access; keep connection secrets out of prompts and logs. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/juspay-xyne-spaces/connect-github-tools-to-an-agent/