Support file uploads (multipart) and Help Center write commands for agent workflows
还没有人认领这个 Issue。
评估
调研方向
Start with the chatwoot api command and its current JSON/raw-body request handling, then inspect the chatwoot hc command structure. Compare the requested multipart POST to /api/v1/accounts/:id/upload and the proposed Help Center write commands with Chatwoot CLI 0.6.1 behavior and related issue chatwoot/chatwoot#14638. Done means the scoped commands support the requested upload and article/category operations with usable output.
由索引模型根据 Issue 内容生成。
描述
Problem
We run self-hosted Chatwoot CE (v4.17) and use AI coding agents with the official CLI (0.6.1, also checked 0.7.0) to manage our Help Center. The agents can read and write articles through chatwoot api, but they cannot add images to an article without a browser session or shell access to the server:
chatwoot apionly sends JSON or a raw body, so it can't do the multipartPOST /api/v1/accounts/:id/upload(attachmentfield) the article editor uses.external_urluploads only work if the image is already on a public URL. Screenshots for a new article usually live in a private repo or on the local disk.- Help Center commands (
chatwoot hc ...) are read-only.
So publishing a short how-to with screenshots currently needs a person to drag images into the web editor, or someone with root on the server running rails runner.
Request
- Multipart file upload in
chatwoot api, e.g.chatwoot api -X POST /upload --form attachment=@./screenshot.png, returning thefile_url/blob_id. This alone would unblock the workflow. - Help Center write commands (nice to have), e.g.:
chatwoot hc upload <file>: upload an image and print a path that can go into article Markdownchatwoot hc article create|update --file article.md --category <slug>chatwoot hc article publish <id>chatwoot hc category create|list
Why
Docs and help articles are a natural fit for agent-driven workflows: write the Markdown in a repo, review it in a PR, then publish with the CLI using a scoped admin token. Image upload is the one step that still needs a human or server access.
Related: chatwoot/chatwoot#14638 (Help Center file attachments in the editor).
- 主要语言
- Go
- 星标
- 11
- 派生
- 5
- 平均合并
- 2 分钟
- 30 天内合并 PR
- 2
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
chatwoot/cli 的其他 Issue
-
难度 5/5 一周以上 新手友好度 48/100
-
难度 5/5 一周以上 新手友好度 35/100
相似的 Issue
-
native
难度 2/5 1-3 小时 新手友好度 72/100
prime-radiant-inc/evener#4839 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
521xueweihan/HelloGitHub#4073 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
goharbor/terraform-provider-harbor#655 · 1 条评论 ·