ZingerLittleBee / Heeler
Native iPhone and iPad console for herdr: watch and drive coding agents on your machines over SSH, in Herdr TUI or the Herdr desktop app (herdr-core), with a real libghostty terminal, native Chat, QR pairing, and push notifications when an agent needs you
- Stars
- 862 stars
- Forks
- 95 forks
- Language
- Swift
- License
- APACHE-2.0
- Created
- Jul 18, 2026
- Last push
- Nov 10, 2026
- Updated
- Nov 10, 2026
Why these Tags: an agent read the README and quoted it
- Coding agent manager from the readme:
Monitor multiple Agents across machines, sorted by who needs you, then open a live terminal or supported Chat conversation to send instructions.
- iOS app from the readme:
Heeler is an independent **herdr mobile client** and agent console for Claude Code, Codex, and other coding Agents on iPhone and iPad.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 9, 2026: +102 stars in 7 days.
Star History
95 days recorded, Aug 8, 2026 – Nov 10, 2026 (UTC). Net change +868 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/ZingerLittleBee/Heeler) Badge
[](https://awesomerepos.com/ZingerLittleBee/Heeler) Timeline
It gained stars on 91 of the 95 days recorded since Aug 8, 2026.
Its largest 7 days were Sep 7, 2026 to Sep 13, 2026: 148 stars.
In the 30 days to Nov 10, 2026 it got 321 stars, 33% more than in the 30 days before.
- Created on the Repository Host
- +52 stars in one day
- Reached 100 stars, 32 days after it was created
- Largest star day recorded: +72 stars
- +27 stars in one day
- Reached 500 stars, 82 days after it was created
- Release v0.1.15
- Release v0.1.16
- Release v0.1.17
- Release builds/0.1.17/40: 0.1.17 (40)
- Release builds/0.1.18/44: 0.1.18 (44)
- Entered the Repository Index: +102 stars in 7 days
- Latest push
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 10, 2026 – Nov 11, 2026. Forks +3. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 11, 2026: new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 11, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 3 tasks for the maintainers of ZingerLittleBee/Heeler.
Improve the Health Facts of the GitHub repository ZingerLittleBee/Heeler. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/ZingerLittleBee/Heeler. A change to the repository can improve each of the 3 items below. Each item gives the measured fact or score, and a task. 1. The newest release tag is a semantic version Fact: The newest release tag is builds/0.1.19/48. Rule: The tag of the newest release has the form 1.2.3 or v1.2.3, with an optional pre-release or build part. There is no data when the repository has no release. Task: Make the next release tag a semantic version (1.2.3 or v1.2.3). Do not change or delete a published tag. If a release tool makes the tags, configure it for semantic versions, and write the version scheme in the contributing guide. 2. A security policy Fact: GitHub finds no security policy (GitHub, 2026-11-11). Rule: GitHub finds a security policy (SECURITY.md in the repository or in the owner's .github repository). Task: Add SECURITY.md at the root or in .github/. Say which versions get security fixes and how to report a vulnerability privately. If GitHub private vulnerability reporting is on, point to it. Ask me for the contact; do not invent one. 3. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-11). Rule: GitHub finds a code of conduct in the repository or in the owner's .github repository. Task: Add CODE_OF_CONDUCT.md at the root with the Contributor Covenant 2.1 text. Change only the contact method. Ask me for the contact; do not invent one. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
3 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-10, 0 days ago. Source
-
Yes: Commits in the last 13 weeks
3886 commits on the default branch in the last 13 weeks (GitHub, 2026-11-11). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 17 of the last 52 weeks (GitHub, 2026-11-11). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 126
- 187
- 165
- 195
- 91
- 149
- 137
- 121
- 176
- 128
- 280
- 240
- 218
- 515
- 348
- 1,051
- 432
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release builds/0.1.19/48 on 2026-11-09, 1 day ago. 10 or more releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is builds/0.1.19/48. Source
-
Yes: A changelog file at the root
CHANGELOG.md at the root (GitHub, 2026-11-11). Source
Security practice
0 of 1 check-
No: A security policy
GitHub finds no security policy (GitHub, 2026-11-11).
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
2 of 3 checksDependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 11, 2026).
No scanned repository names a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 11, 2026: 862 stars, 95 forks, last push Nov 10, 2026, not archived. One of 2 Observations since Nov 10, 2026.