Project Assistant
An AI-powered chatbot that understands your entire project context to answer questions, explain code, and help with development decisions.
Beyond Code Reviews
Ask anything about your project, not just pull requests.
What is Project Assistant?
Project Assistant is an AI chatbot that goes beyond individual pull requests. It can access your entire repository, past code reviews, project documentation, and even connected services like ClickUp and Google Drive to provide comprehensive answers about your project.
Unlike PR-specific chat (@jasper in PR comments), Project Assistant:
- Understands your full codebase structure and patterns
- Remembers conversation history across sessions
- Can reference past code reviews and their outcomes
- Integrates with project management tools
- Learns from your project's AGENTS.md conventions
Getting Started
Access Project Assistant from the Jasper dashboard by clicking the Assistant button in the navigation, or from within a repository's detail page.
Starting a New Session
- Navigate to Assistant in the main menu
- Select a repository to scope your questions (optional)
- Choose which context sources to enable
- Start asking questions!
Based on the codebase, authentication is handled through Laravel Sanctum with a custom
AuthController. Here's how it works:
- - OAuth via GitHub for SSO
- - Email/password with verification
- - API tokens for programmatic access
The main entry point is app/Http/Controllers/AuthController.php...
Context Sources
Project Assistant can gather context from multiple sources to provide informed answers. You can enable or disable sources per session.
GitHub Code
Repository file tree, source code, and code search for finding relevant files.
Enabled by defaultCode Reviews
Recent review history, verdicts, and feedback patterns for the repository.
Enabled by defaultAGENTS.md
Project-specific AI instructions and coding conventions from your repo.
Enabled by defaultClickUp
Search linked ClickUp workspace for tasks, requirements, and project context.
Requires integrationGoogle Drive
Search linked Google Drive folders for specs, designs, and documentation.
Requires integrationWhat You Can Ask
Understanding the Codebase
- "How is authentication implemented in this project?"
- "What design patterns are used in the service layer?"
- "Explain the data flow from API request to database"
- "Where is the payment processing logic?"
- "What are the main entry points for the application?"
Architecture Questions
- "What's the overall architecture of this project?"
- "How are the microservices connected?"
- "What database tables are used and how do they relate?"
- "Where should I add a new API endpoint?"
Development Guidance
- "What's the best way to add a new feature for X?"
- "How do I write tests following this project's patterns?"
- "What conventions should I follow for naming?"
- "How do I set up the local development environment?"
Review History Insights
- "What issues have been flagged in recent reviews?"
- "Are there common patterns in review feedback?"
- "What areas of the code need the most attention?"
- "Has this type of change caused issues before?"
Project Context (with integrations)
- "What are the requirements for ticket CU-1234?"
- "What's documented in the API specification?"
- "Are there any design docs for the checkout flow?"
- "What tasks are related to the payment system?"
Session Management
Project Assistant maintains conversation history in sessions, allowing for multi-turn conversations that build on previous context.
Session Features
| Feature | Description |
|---|---|
| Auto-save | Sessions are automatically saved as you chat |
| History | Up to 100 messages preserved per session |
| Archive | Sessions auto-archive after 7 days of inactivity |
| Resume | Continue any previous conversation where you left off |
| Repository Scope | Sessions can be scoped to specific repositories |
Managing Sessions
- View all sessions from Assistant > Sessions
- Click any session to continue the conversation
- Archive old sessions to keep your list organized
- Delete sessions to remove them permanently
Token Usage
Project Assistant uses tokens from your organization's credit balance. Token usage varies based on:
- Question complexity - Longer questions use more tokens
- Context sources - More sources enabled means more context processed
- Response length - Detailed answers consume more output tokens
- Conversation history - Longer sessions include more context
Tip: Optimize Token Usage
Disable context sources you don't need for your question. For simple code questions, GitHub Code alone is often sufficient.
AGENTS.md Integration
Project Assistant automatically reads and follows your repository's AGENTS.md file
(or similar AI instruction files). This helps the assistant:
- Follow your project's coding conventions
- Understand preferred patterns and libraries
- Provide answers consistent with your team's practices
- Avoid suggesting approaches you've explicitly discouraged
Supported instruction files (in priority order):
AGENTS.md.github/AGENTS.mdcopilot-instructions.md.jasper.mdCLAUDE.md
See Repository AI Guidelines for more information on setting up these files.
API Access
Project Assistant is also available via the Jasper API for programmatic access:
curl -X POST https://heyjasper.ai/api/v1/assistant/chat \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"repository_id": 123,
"question": "How is authentication handled?",
"sources": ["github", "reviews", "agents"]
}'
See the API Reference for complete documentation.
Frequently Asked Questions
Is my code sent to external services?
Code context is sent to our AI provider (Anthropic's Claude) for processing. We follow strict data handling practices and do not use your code for training. See our Privacy Policy for details.
Can I use Project Assistant without a repository?
Yes, you can start a general session without scoping to a repository. However, code-specific context sources (GitHub, Reviews) won't be available.
Why doesn't the assistant know about recent changes?
Context data is cached to improve response times. File tree data refreshes every 30 minutes, and file content every hour. You can manually refresh by starting a new session.
Can I share sessions with my team?
Sessions are currently personal to each user. Team-shared sessions are planned for a future release.