{"full_name":"iflytek/astron-agent","owner":"iflytek","name":"astron-agent","shard":"1","url":"https://github.com/iflytek/astron-agent","description":"Enterprise-grade, commercial-friendly agentic workflow platform for building next-generation SuperAgents.","homepage":"http://astron.ai/","topics":["agent","agentic-workflow","ai","enterprise","low-code","mcp","multi-agent","superagent","workflow","llm","next-gen","orchestration","python","iflytek-astron","agentic-ai"],"tag_pages":["agent","agentic-ai","agentic-workflow","ai","enterprise","llm","low-code","mcp","multi-agent","orchestration","python","workflow"],"language":"Java","license":"Apache-2.0","avatar":"https://avatars.githubusercontent.com/u/26786495?v=4","created_at":"2025-09-19T08:46:01Z","pushed_at":"2026-11-10T12:28:46Z","metrics":{"stars":8932,"forks":913,"watchers":77,"issues":317,"prs":1345,"releases":22,"issues_open":40,"issues_closed":277,"prs_open":25,"prs_closed":126,"prs_merged":1194,"discussions":31},"growth":{"day":{"stars":2,"forks":0,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[8923,8927,8926,8927,8929,8930,8932],"forks":[911,912,912,912,912,913,913],"watchers":[null,77,77,77,77,77,77],"issues_open":[null,38,38,38,39,40,40],"prs_open":[null,25,25,25,25,25,25]},"boards":{},"same_owner":[{"full_name":"iflytek/skillhub","name":"skillhub","shard":"1","boards":{}}],"issues":[{"number":1412,"title":"Expand the documentation FAQ","comments":8,"created_at":"2026-06-15T14:13:16Z"},{"number":1410,"title":"Contribute a workflow example to the gallery","comments":5,"created_at":"2026-06-15T14:13:10Z"},{"number":709,"title":"[FEATURE] Support A2A(agent2agent) Protocol","comments":5,"created_at":"2025-12-09T13:17:26Z"},{"number":1066,"title":"✨ Feature Request: 支持通过拖拽式画布构建“ChatClaw”应用及可视化微调","comments":4,"created_at":"2026-03-23T05:24:25Z"},{"number":1658,"title":"[FEATURE] 资源管理支持从标准 Agent Skills / Agent Plugins 仓库批量导入","comments":3,"created_at":"2026-08-29T12:17:11Z"},{"number":1538,"title":"Feat: Introduce Graph-Based Context Indexing for Multi-Agent Shared Memory","comments":1,"created_at":"2026-07-14T03:50:00Z"},{"number":1067,"title":"✨ Feature Request: 支持 OpenClaw 触发 Astron Agent 调度 RPA 机器人执行安全操作","comments":3,"created_at":"2026-03-23T05:24:26Z"},{"number":507,"title":"希望在 Astron Agent 的工作流画布中增加**向量知识库的写入能力**","comments":3,"created_at":"2025-11-03T13:07:07Z"}],"discussions":[{"number":1360,"title":"当契约成立以后 系统开始追问另一件事","comments":0,"category":"Ideas","created_at":"2026-05-31T14:54:29Z"},{"number":1359,"title":"Astron Agent：Workflow 就是契约的实体化","comments":0,"category":"Ideas","created_at":"2026-05-31T14:52:40Z"},{"number":1138,"title":"为什么我越来越觉得，Agent Workflow 真正碰到真实任务以后，最先暴露出来的不是能力，而是可托付性","comments":1,"category":"Ideas","created_at":"2026-04-04T15:50:22Z"},{"number":933,"title":"Astron Agent & RPA Bi-weekly Report (Jan 19 - Feb 1)","comments":2,"category":"General","created_at":"2026-02-09T13:52:24Z"},{"number":920,"title":"test1","comments":1,"category":"General","created_at":"2026-02-03T10:07:00Z"},{"number":915,"title":"Astron Agent & RPA 社区双周报 (1.19 - 2.1)","comments":0,"category":"General","created_at":"2026-02-02T13:24:17Z"},{"number":914,"title":"Astron Agent & RPA 社区双周报 (1.19 - 2.1)","comments":1,"category":"General","created_at":"2026-02-02T13:08:46Z"},{"number":893,"title":"如何在工作流中得到同一个聊天界面的历史记录","comments":1,"category":"Q&A","created_at":"2026-01-27T10:19:49Z"}],"latest_release":{"name":"Astron Agent v1.1.2 — Security Release","tag":"v1.1.2","published_at":"2026-09-07T06:43:46Z","body":"## Security Release\n\n**Astron Agent v1.1.2 is a security release. Operators running v1.1.1 or earlier should upgrade promptly, especially those running multi-tenant deployments.**\n\n### Workflow code execution and tenant isolation\n\nThis release addresses unsafe workflow code-node execution that could allow an authenticated user with workflow creation permissions to execute code in the workflow service container and access or modify other tenants' data in affected deployments.\n\n- **Affected versions:** `<= v1.1.1`, when using the legacy unsandboxed `local` code executor. Single-tenant deployments are also affected by the code-execution risk.\n- **Patched version:** `v1.1.2`.\n- **Related advisory:** [GHSA-mh3w-4q3f-2fg5](https://github.com/iflytek/astron-agent/security/advisories/GHSA-mh3w-4q3f-2fg5). The security advisory is now public. A CVE identifier has been requested from GitHub and is awaiting assignment.\n\nThe release includes the executor migration in [#1650](https://github.com/iflytek/astron-agent/pull/1650), integrated into `main` through [#1651](https://github.com/iflytek/astron-agent/pull/1651), together with the preceding security hardening:\n\n- Reject unsafe local code execution and use the built-in isolated LangChain/Pyodide executor by default; E2B remains optional.\n- Migrate untouched legacy executor configuration while preserving explicit process-level overrides, including intentional disabling of code nodes.\n- Strengthen authentication on internal Workflow and Tenant service APIs, tenant checks, credential handling, and deployment isolation.\n\n### Additional security fixes\n\n- Prevent server-side request forgery (SSRF) in outbound plugin requests ([#1669](https://github.com/iflytek/astron-agent/pull/1669)).\n- Harden XSS, artifact and sandbox boundaries, and scope CSRF exclusions ([#1643](https://github.com/iflytek/astron-agent/pull/1643)).\n\n## Upgrade Notes\n\n1. Back up your databases, persistent data, and deployment configuration before upgrading.\n2. Update the deployment files and service images together. Use the Compose, service configuration, and gateway configuration shipped with this release, merging your site-specific settings. Updating only the source checkout or only the workflow image does not apply the complete fix.\n3. For Docker Compose deployments, set `ASTRON_AGENT_VERSION=v1.1.2` in `docker/astronAgent/.env`, pull the updated service images, and recreate the stack. Then verify service health and workflow code-node execution. Automated vulnerability scanners may not flag this application-level issue; operators should verify the deployed image versions explicitly.\n4. Review custom code-executor overrides. `CODE_EXEC_TYPE=local` is no longer supported; use the default isolated executor or a supported remote executor. Code that depends on host filesystem, environment, subprocess, or network access may need adaptation to the isolated runtime.\n\n**Container images:** The [v1.1.2 release workflow](https://github.com/iflytek/astron-agent/actions/runs/34090981038) successfully built and pushed all eight core service images, Console Hub, and Console Frontend to GHCR with the `v1.1.2` tag for `linux/amd64` and `linux/arm64`. These images correspond to release commit `189600dd691e8562bd0b9f7112727b107b8a2e10`. Use the explicit release tag for this upgrade; record or pin image digests for reproducibility.\n\nSee the release's [deployment guide](https://github.com/iflytek/astron-agent/blob/v1.1.2/docs/DEPLOYMENT_GUIDE.md) and [configuration reference](https://github.com/iflytek/astron-agent/blob/v1.1.2/docs/CONFIGURATION.md) for deployment requirements and executor migration details.\n\n## Other Changes\n\n- Add Langfuse integration and end-to-end agent traces ([#1607](https://github.com/iflytek/astron-agent/pull/1607)).\n- Harden dependency-aware workflow YAML imports ([#1623](https://github.com/iflytek/astron-agent/pull/1623)).\n- Improve image-build reliability with a reliable PyPI source for RPA and retries for Maven Ce","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}