ChatBoard
ChatBoard: ChatArch kanban board tooling package
快速开始
pip install -e ".[dev]"
chatbd --help
chatbd --tree
chatbd --tree-brief
chatbd --version
chatbd project catalog
python -m pytest -q
python -m build
CLI 文档
chatbd 是 ChatBoard 的辅助管理 CLI。Web UI 是主要产品形态;当前 CLI 只保留 Project 的只读投影、metadata maintenance 和规范化 lifecycle 操作。运行 chatbd --tree 可从真实 Click 注册树输出带参数签名的命令面,chatbd --tree-brief 输出相同命令面但省略参数签名。两者都由 ChatStyle 共享 runtime 渲染。长期文档见 https://arch.gh.wzhecnu.cn/ChatBoard/cli/:
- 命令树、
--tree/--tree-brief回读和命令副作用边界。 ensure创建card.md的推导规则。- area、stage、id、title、summary、tags、links 等 metadata 的符号逻辑。
- Discussion、Archive、Discard 和底层 card move 的移动规则。
chatbd serve的可选登录门禁:--username、--password、--password-file、CHATBOARD_USERNAME和CHATBOARD_PASSWORD;生产/共享环境优先用 ChatEnv,而不是手写~/.config文件。- ChatEnv 对齐:
CHATBOARD_SERVICE_URL、CHATBOARD_HOME、CHATBOARD_BACKENDS_FILE、CHATBOARD_USERNAME/CHATBOARD_PASSWORD、CHATBOARD_API_KEY、default backend token 分层管理;ChatEnv profile 默认在~/.chatarch/envs/Chatboard/,ChatBoard runtime state 默认在~/.chatarch/chatboard/。 - API 自动化可用 Bearer /
X-ChatBoard-Token,登录 cookie 可通过chatenv token refresh Chatboard <profile>写入 runtime token store;chatbd paths可只读回捞当前 ChatEnv/ChatArch-owned 路径和配置开关。 - Web 看板的 card 日期/描述/摘要展示。
- 新增独立
Taskstab:type: task的任务卡片与原有 Projects 看板分开展示。 - 任务管理 CLI:
chatbd project task create/list/status/update/transition/delete,覆盖创建、查看状态、更新、阶段迁移和软删除。
0.2.0 登录与认证
登录后端与登录页复用 ChatLogin;保留可选账号、共享密码及独立 API/executor token,不引入多用户业务权限。会话持久化在 ChatBoard runtime root 的 sessions.sqlite3,由 ChatLogin 负责过期、容量限制与撤销。
- 升级后旧 cookie 需重新登录一次。
CHATBOARD_AUTH_SECRET优先、否则复用密码的签名密钥语义不变;轮换有效密钥立即拒绝旧 cookie。 - 浏览器 cookie 写请求必须同时携带同源
Origin和X-CSRF-Token;先用同一个 cookie 读取GET /api/session,取返回的csrf_token。官方前端自动处理。 - Bearer /
X-ChatBoard-Token自动化无需浏览器 CSRF;真实 executor 操作仍需独立执行 token。 CHATBOARD_LOGIN_PALETTE、CHATBOARD_LOGIN_LAYOUT、CHATBOARD_LOGIN_APPEARANCE可定制共享登录页。
详见登录与认证文档。CI 的常规 pytest 包含完整认证回归、有界 loopback HTTP 登录/退出和 Node.js 前端 fetch 测试。
目录结构
src/:包源码tests/code-tests/:代码测试和历史测试迁移tests/cli-tests/:真实 CLI 测试,doc-firsttests/mock-cli-tests/:mock/fake CLI 测试,doc-firstdocs/:长期维护文档,由 mkdocs 构建
开发说明
扩展脚手架前,先阅读 DEVELOP.md 和 AGENTS.md。
Metadata
Release files for ChatBoard 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| chatboard-0.2.0.tar.gz | 107.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chatboard-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 175.6 kB
Release files / chatboard-0.2.0.tar.gz
| Download URL | chatboard-0.2.0.tar.gz |
|---|---|
| Size | 107.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
babb28114ce24e2aab94506dbc49ed7970415168bf46b979d69e45e32a288b22
|
|
BLAKE2b-256 checksum How to use checksums |
76638024a8ad4def4ca5414a8aa4864e0537962cdd4b4e9e56c82ddab44259f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency logRelease files / chatboard-0.2.0-py3-none-any.whl
| Download URL | chatboard-0.2.0-py3-none-any.whl |
|---|---|
| Size | 68.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3499c2273ddb4291d565382b158d04d70f1f3d726fd70c4fda038daca6cbab01
|
|
BLAKE2b-256 checksum How to use checksums |
3873fb389b976820c8f5dd4ac1e1f11acfeafec036c65633e1289df947949fa3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency log