Activity
Stars and mentions · Last 30 days, Oct 5 – Nov 3
Top repositories
jonwiggins’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside jonwiggins’s account where jonwiggins opened or reviewed pull requests in the past 365 days.
Who noticed jonwiggins
Everyone who starred or forked jonwiggins’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories jonwiggins owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Show HN: Optio – A self-hosted orchestration platform for AI agents Hey HN! I shared Optio here back in March. Originally it was focused on getting swarms of coding agents (claude code/codex) to drive PRs towards a merge by automatically resuming them on CI failures or PR comments. Since then, I've reworked the project to be a general platform for running any kind of AI workflow on your infra by allowing users to configure each component of a possible workflow: When: On demand, a cron schedule, or triggered by external events such as a webhook, slack message, ticket (jira/linear/gh), pagerduty/datadog/alertsmanager/pylon/sentry. Where: In a k8s pod or any machine you have installed the optio daemon on (I use my laptop). Who: Any harness you prefer (Claude Code, Codex, Gemini, Pi, etc.) What/Why: You can format parameters from the triggers directly into the prompts and then configure if the agent should exit, be resumed automatically, or be persistent. You can either define workflows in the web ui or as yaml files that get synced to the orchestrator (ai config-as-code). I've also built native iOS and Android apps so you can connect to your cluster and create/manage agents remotely. The marketing page is at optio.host and the code is still open source at jonwiggins/optio Would love feedback or any thoughts you might have on how I could make it better!