Feature Request:希望支持 Aily CLI 能力
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.3k
- Forks
- 1.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 105
Description
首先感谢团队开源并持续维护 Lark CLI,目前 Lark CLI 已经很好地覆盖了 IM、Docs、Sheets、Base、Calendar、Mail、Tasks 等飞书资源,对于 AI Agent 与飞书协同场景非常有帮助。
不过从 AI 应用开发者的角度来看,目前似乎还缺少对 AIly 相关能力的支持。
当前 Lark CLI 主要解决的是:
- 发消息
- 创建/更新文档
- 操作多维表格
- 查询日历
- 管理飞书资源
但对于 AIly 平台中的核心资源,暂时没有对应的 CLI 能力
对于使用 AI Agent 的开发者来说,越来越多的自动化流程其实是围绕 AIly 构建的,而不仅仅是操作飞书文档或消息。
建议
希望未来能够考虑:
方案一:在 Lark CLI 中增加 AIly Namespace
方案二:提供独立的 AIly CLI
为什么有价值
目前开发者能够通过 Lark CLI 自动化飞书资源:
感谢团队的工作,期待后续能力开放。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Lark CLI namespace and command structure, then identify which Aily resources and operations the API must cover. The issue names no files, commands, or API details, so first confirm whether the work belongs in this repository and define a concrete capability. Done should mean an agreed namespace or standalone CLI scope with commands for the selected Aily workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100