DeepSeek Harness Remote
DeepSeek Harness Remote: DeepSeek Harness 실행 PC와 모바일·PC를 안전하게 연결해 어디서나 작업 이어받기
Keyboard-first terminal launcher for Android
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗#+TITLE: Kolahal #+CAPTION: Kolahal logo [[file:site/public/favicon.svg]] #+END_EXPORT #+SUBTITLE: A keyboard-first terminal launcher for Android
Kolahal (=com.mtwabpin.kolahal=) is a terminal-style home screen for Android 9 and newer. Type a few letters and press Enter to open an app or run a command; every command and its output is kept in a log. It reads RSS and Atom feeds, keeps todos, notes and reminders, controls media and the device, runs your own scripts in Lua 5.4 or JavaScript (QuickJS), and works with the work profile and private space.
#+begin_quote Kolahal is developed with AI assistance. The developers review every change except the tests. #+end_quote
Kolahal's code is still under review. It is young (0.4), parts of it were written with AI assistance, and the review of the codebase as a whole isn't finished. Expect rough edges and changes between versions, keep a [[https://mtwabpin.github.io/kolahal/guides/backup/][backup]], and report what you find.
To install, turn off Play Store → profile → Play Protect → ⚙︎ → Scan apps with Play Protect, then turn it back on. Or use adb install. Once Kolahal is on Google Play, installing it from there avoids the block.
The user guide is at [[https://mtwabpin.github.io/kolahal/][mtwabpin.github.io/kolahal]].
#+begin_src sh ./gradlew :app:assembleRelease # the full APK ./gradlew :app:bundlePlay # the Google Play bundle (-PplayApk :app:assemblePlay: its APK) ./gradlew :app:testDebugUnitTest # JVM tests #+end_src
Kolahal is built with AI assistance, and contributions may use it too. Vibe coding (changes nobody has read, understood or tested, prompted until something seemed to work) isn't accepted.
AI assistance is fine as long as you stay the author:
Pull requests and issues that look generated and unchecked (large unexplained changes, calls to functions that don't exist, claims nobody verified) are closed without review. The same goes for bug reports: reproduce the problem yourself first.
JVM unit tests (=app/src/test=) cover pure logic: parsing, ranking, layout maths and formats. On-device tests (=app/src/androidTest=) cover the script engines and sandbox, commands, storage and backup, and the home and settings screens. The on-device ones install the debug build (package suffix =.debug=) and change its settings; run them on an emulator.
Coverage: 90.8% of the app's code lines (0.4.15), counting a line when either kind of test runs it. It is measured at each release with JaCoCo, on an Android 16 emulator:
#+begin_src sh ./gradlew -Pcoverage :app:createDebugUnitTestCoverageReport :app:createDebugAndroidTestCoverageReport perl tools/coverage.pl # the total, and each package #+end_src