Reported issues for PFC - ITASCA Discrete Element Simulation

Pod holds 6 of 6 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to PFC - ITASCA Discrete Element Simulation.

Most discussed

每一步操作都需要授予权限

无法实现真正的自动化操作，从建模开始每一个步骤都要点击allow，效率比自己做还慢。codex表示无法跳过这个步骤，有没有解决方案

Read the thread · 2026-05-08 · closed · external user · 9 comments

A dialog on screen is invisible to the client

What

A dialog left standing on a running product is invisible to the MCP client. Nothing in the bridge notices it, no tool response mentions it, and from the client's side the only evidence is whatever it was doing not happening.

Filed on its own, without a proposal to click anything, per the note on #55: whether an agent may press Discard on someone's unsaved project is the client's decision, and a wire command no client speaks makes that decision by having made it. The reporting half…

Read the thread · 2026-09-25 · open · outside contributor · 2 comments

start() from a non-main thread kills the GUI process (measured, 3/3)

Summary

Calling itasca_mcp_bridge.start() from a thread other than the GUI thread does not fail loudly. It wedges the whole embedded interpreter and then takes the process down. Reproduced 3/3 on PFC 2D 7.00.161, bridge 0.5.5 as installed.

This matters because "wait for the engine on a thread, then call start()" is the obvious way to write an auto-start hook, and nothing in the API or the guide warns against it.

Why the guard does not catch it

runtime.py L118-119:…

Read the thread · 2026-09-20 · closed · outside contributor · 2 comments

Docs: /health and a port check both look healthy while no task can run

Checked against main @ 222b681 (release 0.9.0), docs/agentic/itasca-mcp-bootstrap.md.

Summary

The guide never tells the reader how to distinguish "bridge is up and executing" from "bridge is up but nothing is being pumped". The Troubleshooting entry at L252–253

- `Connection refused`:
  - Bridge not running in the engine GUI, or port `9001` not available.

implies a port check (or GET /health) is a sufficient readiness test. It is not, and the failure it…

Read the thread · 2026-09-20 · closed · outside contributor · 2 comments

Feature: a supported way to auto-start the bridge

What

A supported way to have the bridge already running when an ITASCA product starts.

Why

The guide's Step 4 telling the user to open the IPython console and type two lines is fine once. It is also the reason a bridge is only up when someone remembers to start it -- which is the wrong default for an MCP server, whose whole point is that an agent can connect to it.

Anyone who wants the bridge permanently has to invent the mechanism, and both obvious ones are traps:

1.…

Read the thread · 2026-09-20 · open · outside contributor · 1 comment

设置之后提示 PFC 侧 bridge 没启动

我按照推荐的方式在codx Windows app设置了MCP，自动配置的过程中反馈’git is not available in this shell and rg is blocked by the environment‘，但是最后似乎仍然配置成功了，运行addon.py也显示接口已经被占用。但是调用pfc_execute_code验证连接时，codex反馈MCP 工具已经加载了，但 PFC 侧 bridge 还没启动，请问这个bridge该怎么启动呢，是我操作过程出现了问题吗

Read the thread · 2026-04-17 · closed · external user · 1 comment

Most recent

The remaining reports are on the project's issue tracker.