TEN Framework PR Hackathon
Build extensions, usecases, and infrastructure for real-time agents.
😸 Event Overview
The TEN Framework PR Hackathon is a 10-day online open-source challenge open to developers worldwide.
During the event, participants contribute directly to the TEN Framework open-source repository by submitting real, mergeable Pull Requests (PRs).
You can:
- Fix bugs
- Build new extensions
- Write or improve documents
- Create usecases
Each merged PR earns points. At the end of the hackathon, top contributors will receive a cash reward.
🗓️ Timeline
Jan 8 – Jan 18, 2026 (Pacific Time)
Online · Global · Open-source
💰 Scoring, Prizes & Participation Terms
🔹 Scoring Rules
- Only PRs submitted during the hackathon period are eligible for scoring
- Hackathon period: Jan 8, 00:00 PT – Jan 18, 00:00 PT
A PR must:
- Be submitted during the event window
- And be successfully merged to earn points
All PRs will be reviewed by the TEN Framework team.
Each merged PR earns points based on its track or official evaluation:
Points are accumulated and used for final ranking and reward redemption.
🔹 Prizes
Participants in the TEN Framework PR Hackathon will be rewarded through:
| Rank | Cash Prize |
|---|---|
| 1st Place | $300 |
| 2nd Place | $200 |
| 3rd Place | $100 |
Note: The first-place prize winner must complete at least one task worth 3 points or more.
📏 Tracks & Rules
The challenge is organized into multiple tracks, covering system-level features, extensions, documentation, and usecases. All submissions will be primarily evaluated based on usability.
1. Challenges & Task Types
The TEN Framework PR Hackathon features two types of challenges:
🔹 Open Challenges
If you have a feature or idea you want to build, you can participate through Open Challenges.
- Open an Issue in the GitHub repository describing the feature or improvement you want to implement with tag
#2026NewYearChallenge, implement the solution and submit your PR - The TEN Framework team will review the issue and assign a score based on its scope and complexity: 1 / 3 / 10 points
- Once the PR is merged, you earn the assigned points
- New extensions/usecases not covered by official tasks
As long as the submission is usable, mergeable, and valuable, it is eligible for scoring.
🔹 Official Tasks
A set of predefined challenges with tag #2026NewYearChallenge designed by the TEN Framework team, covering different difficulty levels and point values.
- 1 point — Bug fixes, tests, documentation
- 3 points — Medium-complexity features and extensions
- 10 points — Usecases
2. Challenge Rules (Official Tracks)
🔹 General Rules
- All submissions must be made via PRs
- Each PR must belong to one track only
- Individuals and teams are welcome to participate
- PRs must:
- Not break existing core functionality
- Follow TEN Framework’s architectural and design principles
- Include at least one runnable or verifiable outcome
🏆 10-Point Tracks (High Difficulty · High Impact)
Designed for contributors delivering complete solutions, covering design, implementation, and real usage scenarios.
Examples: https://github.com/TEN-framework/ten-framework/tree/main/ai_agents/agents/examples
Track A: Usecases
Description: Create other usecases (voice agent templates) for voice interaction scenarios (such as personal-assistant, language coach etc.), enabling developers to create a real-time voice agent with minimal effort.
- Clear example code or demo workflows
- Documentation
- Basic test cases
- Usability
🌟 3-Point Tracks (Medium Difficulty · Official Tasks)
Official issue-based tasks will be assigned. Participants can claim issues from the GitHub repository and submit PRs during the challenge period.
Track B: Extensions/External Tool
Description: Add support for additional LLM/TTS/STT providers or External Tools.
A guide for STT extensions: https://theten.ai/docs/ten_agent_examples/extension_dev/create_asr_extension
- Complete model integration
- No breaking changes to existing model logic
- Documentation
- Basic test cases
- Usability
Track C: Bugfixes & Stability Improvements
Description: Identify and fix real, reproducible issues in TEN Framework.
- Clear problem description and reproduction steps
- Corresponding fix implementation
- Necessary validation or test evidence
- Usability
💪 1-Point Tracks (Low Barrier · High Participation)
Track D: Documentation Improvements
Description: Improve TEN Framework documentation to help new users get started faster.
- From-scratch tutorials
- More language versions
- Common pitfalls and best practices
Participants can also publish related content on external platforms (blogs or social media) and clearly reference the official TEN Framework repository.
- Meaningful documentation improvements
- Clear explanations of core concepts
- Consistent and explicit repository references
- Usability
Track E: Testing (Unit / End-to-End)
Description: Write unit tests or end-to-end tests for TEN Framework to improve overall stability.
- Test code
- A brief explanation in the PR description
- Necessary validation steps
- Usability
🌍 Open Source & Compliance Statement
To maintain a healthy and sustainable open-source community, all participants must follow these principles:
- All submitted code must:
- Comply with the TEN Framework repository’s open-source license
- Not introduce third-party code with incompatible licenses
- Contributions must be:
- Original work
- Clearly compliant with open-source redistribution terms
- The TEN Framework team reserves the right to:
- Make the final decision on whether a PR is merged
- Disqualify submissions that violate project guidelines or policies
✍️ Additional Notes
- Individuals or teams may submit multiple PRs; points are cumulative
- In case of a tie, the following factors may be considered:
- Code quality
- Practical usability
- Community impact
- The TEN Framework team reserves the right to reasonably interpret and adjust the rules if necessary