Skip to content

Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.

chore(release): prepare v0.3.5 (#182)

Robert06226b25d2046f1a
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 19d6005e..47407b0a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,24 @@
Platform releases use `vX.Y.Z` tags and publish `ghcr.io/tencent/loopforge`. LoopForge Local packages use `local-vX.Y.Z` tags and are published by manually running the `release-local` workflow.
+## 0.3.5 — more agent CLIs, parallel SOP branches and a smaller settings menu
+
+- Chat and SOP roles can run ZCode with a personal API key. Personal settings keep a model catalog for Codex, Claude Code and the agent CLIs behind a custom Base URL: fetch the models the service publishes, then pick, reorder and rename them.
+- The SOP orchestration assistant chooses its own CLI and model, and scheduled tasks run as ordinary chat turns on the CLI they were created with, using the project owner's key.
+- SOP branches whose dependencies are ready run together, and rerunning one cancelled branch restores its cancelled siblings without rerunning their upstream.
+- Requirement clarification is optional: new, imported and synced issues no longer start a clarification round, and 待澄清 no longer blocks triggering an SOP.
+- Main Bot lists issues and pull requests, checks PR status, comments and adds labels on GitHub without opening a workspace.
+- The icon rail keeps only daily work; 流程模板, 运行记录 and 定时任务 move into a two-level settings sidebar, MCP, rules and skills share one 能力资产 page, and personal tokens are called 访问密钥.
+- The conversation sidebar marks a reply that finished while you were elsewhere with a blue dot.
+- Opening a workspace reports clone and image-build progress and stops a step that has stopped moving. A failed or interrupted restore is no longer reported as ready, a checkpoint operation that meets an open terminal fails at once, and resuming a new work branch refuses a remote branch someone else published.
+- Quick access explains before the last step when a member cannot bind repositories to the selected project. Issues that cannot be deleted say why, and stages that have not started show no duration.
+- Saving an unchanged workflow no longer creates a revision, and publishing the same content keeps the current version.
+- Malformed sign-ups no longer spend the per-IP login budget, and each server keeps its own password-attempt limits.
+- The image builds with Go 1.26.11 (GO-2026-6859). `scripts/install.sh` offers to install missing curl, Python and the Docker Compose plugin with apt, dnf, yum or Homebrew.
+- LoopForge Local supports DeepSeek Harness (DSH) and Hermes Agent.
+
+Existing installations may apply `migrations/026_assistant_session_reads.sql` and `migrations/027_cli_model_catalog.sql`; the platform also adds these tables and columns on startup.
+
## 0.3.4 — ARM64 platform images and shared CodeBuddy keys
- Platform administrators create accounts and reset passwords under 平台管理 → 成员账号, so teams that turn off self sign-up no longer need the `loopforge-account` command.
diff --git a/README.md b/README.md
index 8181543b..3c61b7da 100644
--- a/README.md
+++ b/README.md
@@ -100,7 +100,7 @@ New accounts join the **LoopForge demo project**, which includes an SOP made onl
<br>
-- **Executors.** Pick **CodeBuddy, Codex or Claude Code** beside the home composer, then a model. Each executor uses its own credentials from personal settings, and every SOP role can choose its executor independently (built-in roles default to CodeBuddy). Requirement clarification, scheduled assistant tasks and AI notification summaries currently use CodeBuddy. The Docker image ships CodeBuddy and Codex; Claude Code installs from npm on first use and is cached, so that first run requires npm access; [native deployments](docs/deployment.md#workers-and-runners) need the CLI for the executor you choose.
+- **Executors.** Pick **CodeBuddy, Codex or Claude Code** beside the home composer, then a model. Each executor uses its own credentials from personal settings, and every SOP role can choose its executor independently (built-in roles default to CodeBuddy). Requirement clarification and AI notification summaries currently use CodeBuddy; scheduled assistant tasks run on the CLI the task selects. The Docker image ships CodeBuddy and Codex; Claude Code installs from npm on first use and is cached, so that first run requires npm access; [native deployments](docs/deployment.md#workers-and-runners) need the CLI for the executor you choose.
- **GitHub is optional.** All built-in generic SOPs run without a repository: product SOPs deliver documents, and new frontend/backend projects deliver source files in the task workspace. Bug fixes still need source code and reproduction details. Connect a repository when you work on existing code or want PRs.
- **Delivering to a repository.** Choose **Connect GitHub** in personal settings, approve the device code on GitHub and pick your repository (the LoopForge OAuth App is built in; no PAT required, manual PAT entry still works). Set executor credentials (or bind a local execution machine), then either run a project SOP or ask Main Bot to change the code and submit a PR/MR.
- **Sandboxes.** In the default Compose installation, SOP runs and conversation workspaces both use Docker sandbox containers started through the host Docker socket. Default sandboxes reuse the installed runtime image, so nothing extra is built after installation; custom Dockerfiles still build their own images. Docker socket access grants control of the host daemon, so this setup is for trusted teams, not untrusted multi-tenant isolation. See [deployment boundaries](docs/deployment.md#accounts). Re-running the installer keeps your data.
diff --git a/README.zh-CN.md b/README.zh-CN.md
index 443b4885..3b5f7be7 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -100,7 +100,7 @@ cd LoopForge
<br>
-- **执行器。** 在首页输入框旁选择 **CodeBuddy、Codex 或 Claude Code**,再选择模型;不同执行器分别使用个人设置里的对应凭据。每个 SOP 角色都可以独立选择执行器(内置角色默认 CodeBuddy)。需求澄清、定时助手任务和通知 AI 汇总目前使用 CodeBuddy。Docker 镜像内置 CodeBuddy 和 Codex;Claude Code 在首次使用时从 npm 安装并缓存,需要能访问 npm;[原生部署](docs/deployment.md#workers-and-runners)需安装所选执行器的 CLI。
+- **执行器。** 在首页输入框旁选择 **CodeBuddy、Codex 或 Claude Code**,再选择模型;不同执行器分别使用个人设置里的对应凭据。每个 SOP 角色都可以独立选择执行器(内置角色默认 CodeBuddy)。需求澄清和通知 AI 汇总目前使用 CodeBuddy;定时助手任务使用任务所选的执行器。Docker 镜像内置 CodeBuddy 和 Codex;Claude Code 在首次使用时从 npm 安装并缓存,需要能访问 npm;[原生部署](docs/deployment.md#workers-and-runners)需安装所选执行器的 CLI。
- **GitHub 可选。** 所有内置通用 SOP 都可以不绑定仓库运行:产品方案交付文档,前后端新项目在任务工作区交付源码;缺陷修复仍需提供待修代码和复现材料。需要修改已有代码或提交 PR 时再绑定仓库。
- **交付到仓库。** 在个人设置中点击「连接 GitHub」,用设备码授权后选择自己的仓库(已内置 LoopForge 授权应用,无需申请 PAT,仍可手动填写 PAT),再配置执行器凭据(或绑定本机执行机器),之后既可以运行一条项目 SOP,也可以直接让 Main Bot 修改代码并提交 PR/MR。
- **沙箱。** 默认 Compose 安装中,SOP 运行和对话工作区都使用 Docker 沙箱容器,由平台通过宿主机 Docker socket 启动;默认沙箱复用已安装的运行镜像,安装后无需再构建;自定义 Dockerfile 仍单独构建。Docker socket 赋予平台控制宿主机 Docker 的权限,因此只适用于可信团队,不构成不可信多租户隔离边界;详见[部署边界](docs/deployment.md#accounts)。重复执行安装脚本会保留已有数据。
diff --git a/compose.yaml b/compose.yaml
index 3f1e1d9a..04647b57 100644
--- a/compose.yaml
+++ b/compose.yaml
@@ -21,7 +21,7 @@ services:
profiles: [platform]
# Published release stack: never builds. Bump the pinned tag (here and in
# AGENTFLOW_ISOLATED_IMAGE) with each release; source builds use compose.dev.yaml.
- image: ${LOOPFORGE_IMAGE:-ghcr.io/tencent/loopforge:0.3.4}
+ image: ${LOOPFORGE_IMAGE:-ghcr.io/tencent/loopforge:0.3.5}
ports:
- "${LOOPFORGE_BIND:-0.0.0.0}:${AGENTFLOW_HTTP_PORT:-8090}:8080"
environment:
@@ -40,7 +40,7 @@ services:
AGENTFLOW_PLATFORM_MCP_URL: ${AGENTFLOW_PLATFORM_MCP_URL:-http://platform:8080}
AGENTFLOW_DOCKER_NETWORK: ${COMPOSE_PROJECT_NAME:-loopforge}_default
AGENTFLOW_LOCAL_SANDBOX: docker
- AGENTFLOW_ISOLATED_IMAGE: ${LOOPFORGE_IMAGE:-ghcr.io/tencent/loopforge:0.3.4}
+ AGENTFLOW_ISOLATED_IMAGE: ${LOOPFORGE_IMAGE:-ghcr.io/tencent/loopforge:0.3.5}
HOME: ${LOOPFORGE_DATA_DIR:?Run scripts/configure.sh first}/home
AGENTFLOW_RUNNER_BINARY: /app/bin/agentflow-runner-{os}-{arch}
AGENTFLOW_GATE_MCP_BINARY: /app/bin/agentflow-gate-mcp-{os}-{arch}
diff --git a/docs/deployment.md b/docs/deployment.md
index 2baa8b1b..383b159f 100644
--- a/docs/deployment.md
+++ b/docs/deployment.md
@@ -35,7 +35,7 @@ The installer checks Docker, Compose, Python 3 and curl. It offers to install mi
Run it as the installation owner, including an ordinary Linux user. If that user cannot access Docker directly, the installer validates sudo and uses `sudo -n docker` consistently for Compose, schema installation and seeds. Before each operation it checks whether sudo credentials expired during a long build, prompting again in a terminal or failing with instructions in unattended mode. It does not require adding the user to the Docker group or logging out. For unattended installations run `sudo -v` first; `LOOPFORGE_YES=1` accepts installation prompts but does not bypass operating-system permissions. Without sudo or Docker access it fails immediately with instructions. Rootless Docker uses its active context's Unix socket; remote Docker contexts need a separately configured deployment because sandbox workspaces are local bind mounts.
-`compose.yaml` is the published-image stack and never builds: `./start.sh`, `scripts/install.sh` and a plain `docker compose --profile platform up` all pull the GHCR release pinned there (currently `ghcr.io/tencent/loopforge:0.3.4`). The pin matches the checkout's migrations and seeds, so check out a release tag when you install. Set `LOOPFORGE_IMAGE` (for example to an `@sha256:` digest) only to override it; a value saved in `.env` takes precedence over later pin changes.
+`compose.yaml` is the published-image stack and never builds: `./start.sh`, `scripts/install.sh` and a plain `docker compose --profile platform up` all pull the GHCR release pinned there (currently `ghcr.io/tencent/loopforge:0.3.5`). The pin matches the checkout's migrations and seeds, so check out a release tag when you install. Set `LOOPFORGE_IMAGE` (for example to an `@sha256:` digest) only to override it; a value saved in `.env` takes precedence over later pin changes.
`./start.sh dev` (or `LOOPFORGE_BUILD_FROM_SOURCE=1 bash scripts/install.sh`) builds this checkout as `loopforge-platform:local` from `compose.dev.yaml`. It saves `COMPOSE_FILE=compose.yaml:compose.dev.yaml` in `.env`, so later runs and plain `docker compose` commands keep using the source build until `./start.sh release`. Source builds reuse npm, Go module and Go compiler caches.