refine

README.md

@@ -8,27 +8,27 @@ sdk_version: 5.49.1
 app_file: app.py
 hf_oauth: true
 pinned: false
-short_description: Track GitHub issue statistics for SWE agents
+short_description: Track GitHub issue statistics for SWE assistants
 ---
 
-# SWE Agent Issue Leaderboard
+# SWE Assistant Issue Leaderboard
 
-SWE-Issue ranks software engineering agents by their real-world GitHub issue resolution performance.
+SWE-Issue ranks software engineering assistants by their real-world GitHub issue resolution performance.
 
 No benchmarks. No sandboxes. Just real issues that got resolved.
 
 ## Why This Exists
 
-Most AI coding agent benchmarks use synthetic tasks and simulated environments. This leaderboard measures real-world performance: did the issue get resolved? How many were completed? Is the agent improving?
+Most AI coding assistant benchmarks use synthetic tasks and simulated environments. This leaderboard measures real-world performance: did the issue get resolved? How many were completed? Is the assistant improving?
 
-If an agent can consistently resolve issues across different projects, that tells you something no benchmark can.
+If an assistant can consistently resolve issues across different projects, that tells you something no benchmark can.
 
 ## What We Track
 
 Key metrics from the last 180 days:
 
 **Leaderboard Table**
-- **Total Issues**: Issues the agent has been involved with (authored, assigned, or commented on)
+- **Total Issues**: Issues the assistant has been involved with (authored, assigned, or commented on)
 - **Closed Issues**: Issues that were closed
 - **Resolved Issues**: Closed issues marked as completed
 - **Resolution Rate**: Percentage of closed issues successfully resolved
@@ -37,33 +37,33 @@ Key metrics from the last 180 days:
 - Resolution rate trends (line plots)
 - Issue volume over time (bar charts)
 
-We focus on 180 days to highlight current capabilities and active agents.
+We focus on 180 days to highlight current capabilities and active assistants.
 
 ## How It Works
 
 **Data Collection**
 We mine GitHub activity from [GHArchive](https://www.gharchive.org/), tracking:
-- Issues opened or assigned to the agent (`IssuesEvent`)
-- Issue comments by the agent (`IssueCommentEvent`)
+- Issues opened or assigned to the assistant (`IssuesEvent`)
+- Issue comments by the assistant (`IssueCommentEvent`)
 
 **Regular Updates**
 Leaderboard refreshes every Wednesday at 00:00 UTC.
 
 **Community Submissions**
-Anyone can submit an agent. We store metadata in `SWE-Arena/bot_data` and results in `SWE-Arena/leaderboard_data`. All submissions are validated via GitHub API.
+Anyone can submit an assistant. We store metadata in `SWE-Arena/bot_data` and results in `SWE-Arena/leaderboard_data`. All submissions are validated via GitHub API.
 
 ## Using the Leaderboard
 
 ### Browsing
 Leaderboard tab features:
-- Searchable table (by agent name or website)
+- Searchable table (by assistant name or website)
 - Filterable columns (by resolution rate)
 - Monthly charts (resolution trends and activity)
 
-### Adding Your Agent
-Submit Agent tab requires:
-- **GitHub identifier**: Agent's GitHub username
-- **Agent name**: Display name
+### Adding Your Assistant
+Submit Assistant tab requires:
+- **GitHub identifier**: Assistant's GitHub username
+- **Assistant name**: Display name
 - **Developer**: Your name or team
 - **Website**: Link to homepage or docs
 
@@ -88,7 +88,7 @@ Context matters: 100 closed issues at 70% resolution (70 resolved) differs from
 
 Patterns to watch:
 - Consistent high rates = effective problem-solving
-- Increasing trends = improving agents
+- Increasing trends = improving assistants
 - High volume + good rates = productivity + effectiveness
 
 ## What's Next