Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Sandbox your local AI agents so they can read/write only what they need
| Date | Stars |
|---|---|
| 2026-08-04 | 1944 |
| 2026-08-06 | 1944 |
| 2026-08-13 | 1979 |
| 2026-08-18 | 2016 |
| 2026-08-19 | 2017 |
| 2026-08-20 | 2018 |
| 2026-08-21 | 2021 |
| 2026-08-22 | 2026 |
| 2026-08-23 | 2030 |
| 2026-08-24 | 2034 |
| 2026-08-26 | 2037 |
| 2026-08-27 | 2038 |
| 2026-08-28 | 2040 |
| 2026-08-29 | 2042 |
| 2026-08-30 | 2043 |
| 2026-08-31 | 2045 |
| 2026-09-01 | 2046 |
| 2026-09-02 | 2049 |
| 2026-09-03 | 2049 |
| 2026-09-04 | 2050 |
| 2026-09-05 | 2050 |
| 2026-09-06 | 2050 |
| 2026-09-08 | 2050 |
| 2026-09-09 | 2053 |
| 2026-09-10 | 2053 |
| 2026-09-11 | 2054 |
| 2026-09-12 | 2055 |
| 2026-09-13 | 2056 |
| 2026-09-14 | 2059 |
| 2026-09-15 | 2060 |
| 2026-09-16 | 2063 |
| 2026-09-17 | 2065 |
| 2026-09-18 | 2068 |
| 2026-09-19 | 2069 |
| 2026-09-20 | 2071 |
| 2026-09-21 | 2073 |
| 2026-09-22 | 2077 |
| 2026-09-23 | 2078 |
| 2026-09-24 | 2079 |
| 2026-09-25 | 2078 |
| 2026-09-26 | 2081 |
| 2026-09-27 | 2083 |
| 2026-09-29 | 2084 |
| 2026-09-30 | 2086 |
| 2026-10-01 | 2086 |
| 2026-10-02 | 2089 |
| 2026-10-03 | 2092 |
| 2026-10-07 | 2093 |
| 2026-10-08 | 2093 |
| 2026-10-09 | 2096 |
| 2026-10-11 | 2098 |
| 2026-10-12 | 2103 |
| 2026-10-13 | 2105 |
| 2026-10-14 | 2105 |
| 2026-10-15 | 2108 |
| 2026-10-16 | 2109 |
| 2026-10-17 | 2110 |
| 2026-10-18 | 2110 |
| 2026-10-19 | 2113 |
| 2026-10-20 | 2114 |
| 2026-10-21 | 2117 |
| 2026-10-23 | 2118 |
| 2026-10-24 | 2119 |
| 2026-10-25 | 2120 |
| 2026-10-27 | 2121 |
| 2026-10-28 | 2123 |
| 2026-10-29 | 2125 |
| 2026-10-30 | 2128 |
| 2026-10-31 | 2129 |
| 2026-11-01 | 2131 |
| 2026-11-02 | 2132 |
| 2026-11-03 | 2133 |
| 2026-11-04 | 2134 |
Today
+1 stars today
This week
+11 stars this week
This month
+42 stars this month
Momentum
30.0
growth rate 0.52%/day
# Agent Safehouse [](https://github.com/eugene1g/agent-safehouse/actions/workflows/tests-macos.yml) [](https://github.com/eugene1g/agent-safehouse/actions/workflows/e2e-agent-tui-macos.yml) [](LICENSE) Sandbox your LLM coding agents on macOS so they can only access the files and integrations they actually need. Agent Safehouse uses `sandbox-exec` with composable policy profiles and a deny-first model. It includes profiles for major coding agents and app-hosted agent workflows while keeping normal development usage practical. ## Install Homebrew: ```bash brew install eugene1g/safehouse/agent-safehouse ``` Standalone script: ```bash mkdir -p ~/.local/bin curl -fsSL https://github.com/eugene1g/agent-safehouse/releases/latest/download/safehouse.sh \ -o ~/.local/bin/safehouse chmod +x ~/.local/bin/safehouse ``` ## Philosophy Agent Safehouse is designed around practical least privilege: - Start from deny-all. - Allow only what the agent needs to do useful work. - Keep developer workflows productive. - Make risk reduction easy by default. It is a hardening layer, not a perfect security boundary against a determined attacker. ## HOME access by default `HOME_DIR` is used to render precise home-relative rules in the assembled policy. By itself, it does not grant recursive read access to your home directory. `WORK_DIR` similarly exposes the selected workdir to built-in and appended policy rules through `workdir-literal`, `workdir-subpath`, and `workdir-prefix`. Relative helper arguments begin with `/`, letting a reusable policy target files such as `<workdir>/.env` without hardcoding an absolute project path. Default Safehouse behavior is narrower: - metadata-only traversal on `/`, the path to `$HOME`, and `$HOME` itself so runtimes can probe explicitly allowed home-scoped paths - directory-root reads for `~/.config` and `~/.cache` so tools can discover XDG locations - a few explicit home-scoped files/directories from always-on profiles, such as git/ssh metadata and shared agent instruction folders In practice, `stat "$HOME"` can succeed while `ls "$HOME"` and `cat ~/secret.txt` still fail unless a more specific rule grants that path. If you want to remove even the default home exceptions, use `--append-profile`; appended profiles load last, so their deny rules can narrow earlier defaults. ## Built-In System Path Resolution Safehouse's built-in `profiles/*` modules may include macOS compatibility paths such as `/etc`, `/private/etc/resolv.conf`, or `/private/etc/localtime`. At policy render time, Safehouse resolves built-in absolute paths from `allow file-read*` rules and emits matching grants for the real target path when the authored path is a symlink. That keeps host-specific system files working without broadening the source profiles to recursive `/private/etc` access. Current scope is intentionally limited to built-in absolute `literal` and `subpath` read grants. User-provided path grants still normalize separately, and writable or metadata-only built-in rules are not auto-expanded by this mechanism today. ## Documentation - Website: [agent-safehouse.dev](https://agent-safehouse.dev) - Docs: [agent-safehouse.dev/docs](https://agent-safehouse.dev/docs/) - Policy Builder: [agent-safehouse.dev/policy-builder](https://agent-safehouse.dev/policy-builder) ## Machine-Specific Defaults If you keep shared repos, caches, or team folders in machine-specific locations, keep those settings out of project config and put them in a shell wrapper plus a local appended profile. This lets you define your own sane defaults once and reuse them from `claude`, `codex`, `amp`, or app launchers: POSIX shells (`zsh` / `bash`):
Excerpt of 7,088 characters
Read on GitHub
187
22
21
4
3
3
3
2
1
1
1
1
1
1
1
CL Kao · Recce · United States
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:7b1847663940851c, topic:ai-agents, desc:ai agents
matched fp:7b1847663940851c, topic:llm