jnMetaCode / agency-orchestrator
🚀 One sentence → your one-person company of AI experts → complete deliverable in minutes. 276 CN + 184 EN + 5 more languages (ko/ru/pt-BR/id/ar) · zero-code YAML · auto-verified acceptance · Web Studio / Desktop / Docker · 15 LLM providers (11 key-free). 一句话组建你的「一人公司」AI 专家团队，几分钟交付完整方案；验收自动核验，网页 / 桌面 / Docker 全渠道。
Read the English README on GitHub (README.en.md, a file of the repository)
- Stars
- 2,468 stars
- Forks
- 331 forks
- Language
- TypeScript
- License
- APACHE-2.0
- Created
- Mar 21, 2026
- Last push
- Nov 11, 2026
- Updated
- Nov 12, 2026
Admitted to the Repository Index on Nov 11, 2026: 2,461 stars on 2026-11-11.
Star History
189 days recorded, May 8, 2026 – Nov 12, 2026 (UTC). Net change +1,749 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/jnMetaCode/agency-orchestrator) Badge
[](https://awesomerepos.com/jnMetaCode/agency-orchestrator) Timeline
It gained stars on 188 of the 189 days recorded since May 8, 2026.
Its largest 7 days were May 19, 2026 to May 25, 2026: 150 stars.
In the 30 days to Nov 12, 2026 it got 121 stars, 3% fewer than in the 30 days before.
- Created on the Repository Host
- +27 stars in one day
- Reached 1,000 stars, 64 days after it was created
- +28 stars in one day
- Largest star day recorded: +29 stars
- Release desktop-v0.4.10
- Release desktop-v0.4.11
- Release desktop-v0.4.12
- Release desktop-v0.4.13
- Release desktop-v0.4.14
- Entered the Repository Index: 2,461 stars on 2026-11-11
- 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 12, 2026 – Nov 13, 2026. Forks +2. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 13, 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 reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of jnMetaCode/agency-orchestrator.
Improve the Health Facts of the GitHub repository jnMetaCode/agency-orchestrator. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/jnMetaCode/agency-orchestrator. A change to the repository can improve each of the item 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 desktop-v0.4.14. 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. 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
2 of 4 checks (2 without data)-
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-11, 2 days ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
1 of 3 checks (1 without data)-
Yes: A release in the last 365 days
Newest release desktop-v0.4.14 on 2026-10-21, 23 days 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 desktop-v0.4.14. Source
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
1 of 3 checks (2 without data)-
Yes: A licence
GitHub finds the licence APACHE-2.0. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Observations
Latest Observation, Nov 13, 2026: 2,468 stars, 331 forks, last push Nov 11, 2026, not archived. One of 2 Observations since Nov 12, 2026.