This guide will help you set up the GitHub Explorer project locally for development.
Before you begin, ensure you have the following installed:
- Node.js 18+ or Bun (recommended)
- Git
- A GitHub account with access to create Personal Access Tokens
- A Tambo AI account with API access
git clone <your-repo-url>
cd tambo-githubThis project uses Bun as the package manager (recommended):
bun installAlternatively, you can use npm or pnpm:
npm install
# or
pnpm installCopy the example environment file:
cp .env.example .envEdit .env and add your API keys:
NEXT_PUBLIC_TAMBO_API_KEY=your_NEXT_PUBLIC_TAMBO_API_KEY_here
NEXT_PUBLIC_TAMBO_URL=https://api.tambo.co
GITHUB_TOKEN=your_github_personal_access_token_herenpx tambo initbun dev
# or
npm run dev
# or
pnpm devOpen http://localhost:3000 in your browser.
- Go to GitHub Settings > Developer settings > Personal access tokens
- Click "Generate new token (classic)"
- Give it a descriptive name (e.g., "Tambo GitHub Explorer")
- Select the following scopes:
public_repo- Access public repositoriesrepo- Full control of private repositories (if needed)read:user- Read user profile datauser:email- Access user email addresses
- Click "Generate token"
- Copy the token immediately (you won't see it again)
- Add it to your
.envfile asGITHUB_TOKEN
- Visit tambo.co and sign up/log in
- Navigate to your API settings
- Generate a new API key
- Copy the key and add it to your
.envfile asNEXT_PUBLIC_TAMBO_API_KEY
# Development server
bun dev
# Build for production
bun run build
# Start production server
bun start
# Type checking
bun run type-check
# Linting
bun run lint- Repository Search: Search for GitHub repositories
- Repository Analysis: Get AI-powered insights
- Issue Management: View and classify issues
- PR Analysis: Analyze pull requests with AI
- Release Notes: Generate automated release notes
| Variable | Description | Required |
|---|---|---|
NEXT_PUBLIC_TAMBO_API_KEY |
Your Tambo AI API key | Yes |
NEXT_PUBLIC_TAMBO_URL |
Tambo API endpoint | Yes |
GITHUB_TOKEN |
GitHub Personal Access Token | Yes |
1. "Invalid API Key" Error
- Verify your Tambo API key is correct
- Ensure the key has proper permissions
- Check that
NEXT_PUBLIC_TAMBO_API_KEYis set in.env
2. GitHub API Rate Limiting
- Ensure your GitHub token is valid
- Check rate limit status in browser dev tools
- Consider using a token with higher rate limits
3. Build Errors
- Run
bun run type-checkto identify TypeScript issues - Ensure all dependencies are installed
- Clear
.nextfolder and rebuild
4. Environment Variables Not Loading
- Ensure
.envis in the project root - Restart the development server after changes
- Check that variables start with
NEXT_PUBLIC_for client-side access
- Hot Reload: The development server supports hot reload for most changes
- TypeScript: The project uses strict TypeScript - fix type errors promptly
- Tailwind CSS: Use existing utility classes for consistent styling
- Component Structure: Follow the existing pattern for new components
# Install dependencies
bun install
# Build the application
bun run build
# Start production server
bun startFor production deployment:
- Set all required environment variables
- Use production-grade GitHub tokens
- Configure proper CORS settings for Tambo API
- Set up monitoring and logging
- Follow the existing code style and patterns
- Add TypeScript types for all new code
- Test new features thoroughly
- Update documentation as needed
- Follow the commit message conventions
For issues and questions:
- Check the Tambo AI documentation
- Review GitHub API documentation
- Check existing issues in the repository
- Create a new issue with detailed information
Happy coding! 🚀