The most powerful AI agent and AI chat software on Android/Operit是一款Android上能力最为强大、发展最久的AI Agent
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 57%
Response Time: -
First Timer Success: 50%
AAswordman/Operit has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in AAswordman/Operit respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 63.9 places AAswordman/Operit in the A tier.
The external contributor pull request merge rate for AAswordman/Operit is 56.5%, based on public PR activity from non-core contributors.
AAswordman/Operit currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in AAswordman/Operit. Reviews community pull requests with focus on project quality.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/AAswordman/Operit?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (71% approval). Large PRs (>500 lines) take ~115 hours (25% approval). Keep your diff compact for rapid review.
问题 发送聊天记录时，加载之前的聊天记录会导致新聊天记录被隐藏，从而使发送失败。 建议 页面滑动时自动加载聊天记录 多选聊天记录时，加载的聊天记录自动缓存不被隐藏直到多选操作结束
使用场景 / 痛点 在做家居自动化、多设备数据汇总、个人数据看板这类玩法时，常常需要把设备的运行状态（前台 app、最近通知、位置、电量等）周期性地推送到一个外部服务（自建后端 / 数据库 / Home Assistant 等）。 Operit 已经内置了采集这些数据的工具（app 使用时长 / 通知 / 定位 / 电量），但目前这些数据只能在对话中由 AI 主动调用时才拿得到，没有办法在后台按固定周期自动上报到外部服务。 建议 增加一个「设备状态定时上报」的后台能力： 在设置里增加开关、上报间隔（如 15 分钟）、目标 URL、自定义 Header 后台用 Service + WorkManager 定时采集设备状态（前台 app / 最近通知 / 位置 / 电量等） 打包成 JSON，POST 到用户配置的 URL 这样无需对话触发，就能把设备状态持续同步到外部，方便做自动化和数据看板。 实现难度（个人判断） 采集能力
比如我在一个供应商里添加了若干款模型，它们的上下文，是否支持多模态等参数均不一样，但模型配置里都是一键对全部模型启用设置。希望能单独对一个模型的参数进行配置
回看历史对话时，之前发送的图片显示"已过期"无法查看。因为 ImagePoolManager 在应用启动时清空缓存 (clearDiskCache())，并在消息发送后立即删除图片 (removeImagesFromLastUserMessage())。 消息数据库中仍保留 <link type=image id=UUID> 引用，但对应的图片文件已被删除。 建议方案： 在设置中增加一个用户可选开关（如"保留聊天图片"），默认关闭（保持现有行为不变） 开启后： 启动时不清理被现有消息引用的图片 发送后保留图片缓存（或复制到持久目录） 使用场景： 将 Operit 用于长期对话交互的用户，喜欢回看聊天记录。图片过期导致对话回忆不完整，影响体验连续性。 Source: app/src/main/java/com/ai/assistance/operit/util/ImagePoolManager.kt (line ~692) Storage format: <UUID>.dat (base64 JPEG) + <UUID>.meta (JSON metadata) Three cleanup triggers currently exist: initialize() → imagePool.clear() + clearDiskCache(
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to AAswordman/Operit, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of AAswordman/Operit acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.5% were successfully merged into the primary branch.
AAswordman/Operit has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 63.9 places AAswordman/Operit in the Welcoming tier.
The external pull request merge rate is 56.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AAswordman/Operit currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for AAswordman/Operit are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.