SeasX / SeasAGI
Local LLM API Intelligent Gateway — Open-source client + Server Open Core model, unified management of multiple LLM Provider channels, providing intelligent routing, session stickiness, cost optimization, full-chain observability, and team collaborative governance.
- Stars
- 176 stars
- Forks
- 5 forks
- Language
- Go
- License
- AGPL-3.0
- Created
- Jul 2, 2026
- Last push
- Nov 10, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- LLM gateway from the readme:
Fallback / Round-Robin / Sticky strategies, Combo step-chain orchestration (primary → backup → last-resort)
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: +164 stars in 7 days.
Star History
134 days recorded, Jul 1, 2026 – Nov 11, 2026 (UTC). Net change +176 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/SeasX/SeasAGI) Badge
[](https://awesomerepos.com/SeasX/SeasAGI) Timeline
It gained stars on 8 of the 134 days recorded since Jul 1, 2026.
Its largest 7 days were Nov 2, 2026 to Nov 8, 2026: 164 stars.
- +2 stars in one day
- Created on the Repository Host
- +7 stars in one day
- Pre-release 0.1.0
- Reached 100 stars, 128 days after it was created
- Largest star day recorded: +163 stars
- Entered the Repository Index: +164 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 3 Observations, Nov 10, 2026 – Nov 12, 2026. Forks 0. AwesomeRepos saw a new push on 1 of 2 days.
- Nov 11, 2026: new push
- Nov 12, 2026: no 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 SeasX/SeasAGI.
Improve the Health Facts of the GitHub repository SeasX/SeasAGI. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/SeasX/SeasAGI. 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. A changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-11). Rule: The root of the default branch has a file named CHANGELOG, CHANGES, HISTORY, NEWS, RELEASE, or RELEASES, with no extension or with .md, .markdown, .rst, .txt, or .adoc. Release notes on GitHub releases do not count. Task: Add CHANGELOG.md at the root of the default branch. Write one section for each published release, newest first, from the GitHub releases, the Git tags, and the commit history. Do not invent changes. If the project uses a release tool (for example Changesets, release-please, or semantic-release), configure it to update this file for each release. 2. A contributing guide Fact: GitHub finds no contributing guide (GitHub, 2026-11-11). Rule: GitHub finds a CONTRIBUTING file in the repository or in the owner's .github repository. Task: Add CONTRIBUTING.md at the root, in docs/, or in .github/. Tell a contributor how to set up the project, run the tests, and propose a change. Use the real commands of this repository (package scripts, Makefile, CI workflows). 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, 1 day ago. Source
-
Yes: Commits in the last 13 weeks
49 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
- 10
- 3
- 5
- 4
- 3
- 0
- 3
- 5
- 9
- 2
- 0
- 2
- 3
- 6
- 7
- 2
- 3
- 2
- 5
Releases
2 of 3 checksSecurity practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-11). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
1 of 3 checks-
Yes: A licence
GitHub finds the licence AGPL-3.0. Source
-
No: A contributing guide
GitHub finds no contributing guide (GitHub, 2026-11-11).
-
No: A code of conduct
GitHub finds no code of conduct (GitHub, 2026-11-11).
Dependencies 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 12, 2026: 176 stars, 5 forks, last push Nov 10, 2026, not archived. One of 3 Observations since Nov 10, 2026.