jev-chat/jev-chat-jarvis

装在手机上的对话副驾:在微信 / QQ / X / 飞书里读懂对方、给出候选回复、一键填入输入框,发不发由你。非侵入,只读屏幕,不 hook 不改包。

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 hours ago
Added to GitGenius on September 22nd, 2026
Created on September 21st, 2026
Open Issues & Pull Requests: 38 (+1)
GitHub issues: Enabled
Number of forks: 914
Total Stargazers: 4,396 (+145)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.4 hours
Mean response time: 2.9 hours
90th percentile: 15.0 hours
Tracked items: 7

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 14
Closed in 7 days: 1
Avg open age: 0 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 14
Closed in 7 days: 1
Comments in 7 days: 20
Events in 7 days: 22

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Jev-Chat Jarvis is a chat assistant for Android that provides suggested replies within messaging applications.

The tool addresses the challenge of composing thoughtful responses in real-time conversations by reading the chat context from the screen and generating candidate replies using a language model. It operates non-invasively through Android's accessibility service, reading only what appears on screen without modifying the target applications or intercepting their data. Users can review the suggested replies and optionally insert one into the input field with a single tap, maintaining full control over whether to send the message.

The project suits developers building productivity tools for Android or those interested in accessibility-service-based integrations. It works across multiple messaging platforms including WeChat, QQ, X, and Feishu. The non-invasive approach means it functions without requiring root access, package modification, or hooking, making it compatible with standard Android devices and applications that would otherwise reject modified versions.

The project shows consistent development activity with regular commits addressing bug fixes and feature refinements. Work spans multiple areas including core functionality improvements, user interface adjustments, and platform-specific compatibility updates. The codebase receives ongoing maintenance with attention to both new capabilities and stability of existing features.