# Reported issues for io.github.JUNKDOGE-JOE/ae-mcp

Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [io.github.JUNKDOGE-JOE/ae-mcp](/mcp/io-github-junkdoge-joe-ae-mcp).

## Most discussed

### fix(opencode): 流式文本被工具/问题事件截断并发生显示顺序错乱

## 环境

- Windows x64
- After Effects 2026 v26.3
- ae-mcp v0.10.2
- OpenCode CLI v1.18.22
- OpenCode Provider 通道

## 现象

OpenCode 在流式回复期间调用工具并弹出问题卡时：

1. 工具状态会插入助手正文中间。
2. 同一段文字会在任意字符位置断开。
3. 用户已经回答问题后，问题之前应当显示的文字才继续出现。
4. UI 仍可能显示“等待模型回复”。

实际会话中，同一个单词被拆开：

- `ai-text :15` 结尾：`globalA`
- `question :16`：状态已经是 `answered`
- `ai-text :17` 开头：`lpha 0.7 ... 两件事需要你拍板`

因此最终显示顺序变成：

```text
globalA
[问题卡：已回答]
lpha 0.7 ... 两件事需要你拍板
```

## 可能根因

`createDeltaRedactor()` 会根据敏感值长度保留一段尾部缓冲。

OpenCode 的 `messa

[Read the thread](https://github.com/JUNKDOGE-JOE/after-effects-mcp/issues/322) · 2026-08-25 · closed · external user · 1 comment

### feat(windows): ZXP 至少内置 OpenCode，并让“重新检测”无需重启 AE

## 问题

在 Windows x64 + After Effects 2026 v26.3 上安装 v0.10.2 ZXP/AEX 后，面板虽然提供 Claude Code、Codex CLI、OpenCode 三个通道，但全新环境中可能一个都不可用，首次配置成本较高。

实际遇到的流程：

- Claude Code 安装到 `%USERPROFILE%\.local\bin\claude.exe` 后，还需要用户手动修改 PATH。
- OpenCode 官网首先给出的是 `curl ... | bash`，无法直接在原生 PowerShell/CMD 中使用；改用 Chocolatey/Scoop/npm 又要求用户预先安装额外工具。
- 安装 CLI 或修改用户 PATH 后，面板点击“重新检测”仍检测不到新环境；必须完全退出并重新启动 After Effects 后才能识别。

最后一点可能是因为 CEP/After Effects 进程一直使用启动时继承的旧环境变量，而“重新检测”只读取了当前进程的 `process.env.PATH`。

## 建议

1. **ZX

[Read the thread](https://github.com/JUNKDOGE-JOE/after-effects-mcp/issues/321) · 2026-08-25 · closed · external user · 0 comments

### compat: ae.skillUse wraps legacy JSON results and can contradict nested ok status

## Summary

The `ae.skillUse(execute=true)` response contract changed when legacy skill execution was routed through the Tool Library engine.

In v0.9.0, the parsed JSX result was returned directly. In v0.9.5 and current `main`, `execute_legacy_skill()` always returns a new success envelope and places the parsed legacy result under `result`.

This removes previously top-level fields and can produce a contradictory response where the outer `ok` is `true` while the executed legacy skill returned `

[Read the thread](https://github.com/JUNKDOGE-JOE/after-effects-mcp/issues/269) · 2026-08-17 · closed · external user · 1 comment

### tool-library: legacy skill argsSchema rejects per-property description metadata

## Summary

Legacy skills can store per-argument metadata in `args_schema`, and `SkillStore` accepts this structure. After legacy skills are projected into Tool Library artifacts, `validate_args_schema()` applies a keyword allowlist that does not include the standard JSON Schema annotation `description`.

As a result, a legacy skill can be loaded and rendered by the skill layer but fail when the same skill passes through the Tool Library / `ae.skillUse` execution path.

## Affected versions

- a

[Read the thread](https://github.com/JUNKDOGE-JOE/after-effects-mcp/issues/268) · 2026-08-17 · closed · external user · 1 comment

### status(windows): loopback /health probe inherits proxy environment and can report false HTTP 502

## Summary

`ae.diagnose` performs a raw `GET <bridge-url>/health` in `packages/core/ae_mcp/handlers/status.py::_probe_host()`. The `httpx.AsyncClient` uses the default `trust_env=True`, so a loopback-only request can inherit `HTTP_PROXY` / `HTTPS_PROXY` / `ALL_PROXY` and be routed through a local or corporate proxy.

When `NO_PROXY` does not cover the bridge address, the diagnostic can report `host.reachable=false` with `HTTP 502` even though the local bridge and the normal execution path are h

[Read the thread](https://github.com/JUNKDOGE-JOE/after-effects-mcp/issues/267) · 2026-08-17 · closed · external user · 1 comment

### Windows v0.9.5 follow-up: composer collapse, timeout safety, result serialization, preview/snapshot and approval defaults

## Summary

After applying the `sidecar + shared` workaround from #239 on a real Windows installation, I continued testing the panel against After Effects and found several independent reliability issues. I am separating confirmed runtime facts from hypotheses below.

Environment used for the tests:

- Windows x64
- Adobe After Effects 2026 v26.3
- ae-mcp panel/host v0.9.5
- Node.js v24.18.0
- local service: `127.0.0.1:11488`

The main Claude → ae-mcp → After Effects execution path is working af

[Read the thread](https://github.com/JUNKDOGE-JOE/after-effects-mcp/issues/243) · 2026-08-13 · closed · outside contributor · 1 comment

### previewFrame: reports nominal comp size instead of the real PNG size, and reads the PNG while AE is still writing it

`ae.previewFrame` fails for me on every capture, with two different error messages under the same conditions. Both trace back to `preview_viewer.jsx` reporting the comp's **nominal** size and `_wait_for_png()` accepting a PNG that AE is still writing. I have a working local patch and would be happy to open a PR if the approach looks right to you.

## Environment

- ae-mcp **v0.9.5** (`636d6f6`), installed via `uv tool install` from this repo
- Backend `HttpBridge` (`ae_status`: `nativeExecutionP

[Read the thread](https://github.com/JUNKDOGE-JOE/after-effects-mcp/issues/242) · 2026-08-13 · closed · outside contributor · 1 comment

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/JUNKDOGE-JOE/after-effects-mcp/issues).