!StarSling Demo

👋 Introduction

StarSling is an open-source developer homepage with AI agents that tackle the 20% of engineering toil that happens outside the editor – fixing exceptions, chasing CI failures, updating docs, and more.

Today, it unifies some of your favorite dev tools (Sentry, GitHub, Linear, etc.) into a single command-center UI and integrates with agentic Sentry AI workflow for fixing exceptions: click Autofix on a Sentry issue and StarSling triggers the Sentry agent to analyze the exception, create a fix, and create a pull request in GitHub – no context-switching required.

Built on top of the Backstage backend and powered by Mastra MCP for orchestrating agentic workflows, StarSling is the foundation for the agentic internal developer portal (IDP) of the future.

✨ Key Features

• Dev Tools Agents – Autofix Sentry exceptions, and soon: merge GitHub PRs and close Linear tickets with one click.
• Unified Homepage – View PRs, exceptions, and tickets from all your tools in one place.
• Backstage-Compatible – Reuses the Backstage APIs and backend so existing plugins work out-of-the-box.
• Mastra Orchestration – Uses Mastra MCP to chain multi-tool agent workflows.
• Extensible – Bring your own agents or dev tool integrations via MCP servers.

🛠️ Basic Product Usage

Start the dev server and open http://localhost:3000 – you’ll see your open GitHub PRs, Sentry issues, and Linear tickets. When a new exception appears, click Autofix to let StarSling + Sentry generate a PR and close the associated ticket.

🚀 Getting Started (Local Setup)

1. Clone the repository

   git clone https://github.com/starslingdev/starsling.git
   cd YOUR_REPO
   

2. Install dependencies

   pnpm install
   

3. Start Supabase (Database)

   # Spin up local Supabase containers
   pnpm supabase:start
   
   # Apply latest migrations
   pnpm db:push
   
   # (Optional) Seed demo data
   pnpm db:seed
   

4. Configure Environment

   cp .env.example .env
   cp app-config.local.yaml.example app-config.local.yaml
   # Edit the .env and app-config.local.yaml files with your secrets (Supabase keys, GitHub tokens, etc.)
   

5. Run the development servers

From the root directory, just run:

pnpm dev

The web app (apps/web) will be available at http://localhost:3000. A script (apps/local-sync) will run in the background to sync your latest Github, Linear, and Sentry data. The Backstage app (apps/backend) will be available at http://localhost:7007.

🏗️ Monorepo Structure

Path	Description
apps/web	Next.js (App Router) with API routes and Supabase integration
apps/backend	Backstage backend configured with Github auth and catalog plugins
packages/eslint-config	Shared ESLint rules
packages/typescript-config	Shared tsconfig.json bases
packages/mastra-backend	Backstage backend plugin for Mastra based chat and MCP
packages/ai-common	Backstage common (isomorphic) plugin for Vercel's ai-sdk and utilities

root
├─ apps/
│  └─ web/
├─ packages/
│  ├─ eslint-config/
│  ├─ typescript-config/
│  ├─ mastra-backend/
│  └─ ai-common/
└─ .github/

🖥️ System Requirements

• Node.js – v20 (Requirement of the Backstage)
• Package Manager – pnpm v8+
• Docker Desktop – v20.10+ (for Supabase)

Integrations

🤝 Contributing

We love contributions! Please read our CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests.

---