Feature request: support saving Feishu Report/日报 content as a draft without submitting
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17.3k
- Forks
- 1.4k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 105
Description
Request
Could lark-cli support creating or updating a Feishu Report (汇报/日报) draft without submitting it?
This would enable an agent or local automation to prepare a daily report in the user's real Feishu Report draft, while leaving the final review and submission entirely to the user. Sending the content through IM or creating a cloud document is not equivalent to a Report draft.
Current limitation
In lark-cli 1.0.76, there is no report domain. The currently documented Report OpenAPI surface appears to expose rule/task queries, but not an API for creating, updating, or saving a draft. If this capability requires a new upstream Feishu OpenAPI, please consider tracking or coordinating that dependency as part of this request.
Suggested CLI design
# Create or update today's draft; never submit
lark-cli report +draft-upsert \
--rule-id <rule_id> \
--report-date 2026-07-23 \
--markdown-file ./daily-report.md \
--as user \
--idempotency-key daily-report-20260723
# Read the saved draft back for verification
lark-cli report +draft-get \
--rule-id <rule_id> \
--report-date 2026-07-23 \
--as user
Useful requirements:
- User identity support.
- Create/update a draft without triggering submission or notifications.
- Structured fields and Markdown/plain-text input.
- Idempotent update behavior.
- Read-back verification.
--dry-runsupport.- Submission must be a separate, explicit command such as
report +submit, classified as a write/high-risk action.
Use case
A user asks an agent to collect verified daily work evidence, write the daily report, and place it in Feishu's native 日报 draft for manual review. The user explicitly does not want the agent to submit it or send it as an IM message.
Thank you for considering this capability. It would close an important human-in-the-loop workflow gap: automation prepares the report, while the user retains final control over submission.
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 current documented Feishu Report OpenAPI surface and the existing lark-cli command structure; the payload notes that version 1.0.76 has no report domain. Confirm whether upstream APIs support draft creation, updates, and read-back before designing the commands. Done means a supported implementation can prepare and verify a draft without submission, with explicit submission remaining separate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100