Feedback on openfox MCP usage

[DavidBabel]

I had some time to try out the MCP, and it is an interesting approach, but it does not works as expected in openfox, and there is few things that could be improved to make it more usable.
My idea was to build an orchestrator agent to manage sessions, but it's not possible yet.

Just a bit of context : I run my local on a single machine, with limited capabilities. I cannot run 2 models simultanesly, and sometime not even 2 sessions. Most of the issue comes from that.

• For this particular reason, the session name extraction stuggle sometime my LLM for few seconds with the 2 parallele requests.
• I stuggle a lot with the fact that the sessions created and any action automatically "starts" the works of the created session.
  If I create a session, it starts working immediatly.
  If I launch a workflow, it starts working immediatly.
  If I send a message, it starts working immediatly.

The problem is, the Orchestrator needs to itself "finish" some task before the other session should start, and I did not find out how to do that.
I am missing a "pending" state on the new created session, that could help.

• The openfox MCP server itself does not start properly with openfox. You need to turn it off and on each time you want to use it after openfox boot. This is something I had experienced with many other agents over time, I don't know why.
  So most of the time on boot the orchestrator fails to find it's tools if some tasks are started immediatly.

• The new session created does not refresh in the session list. Looks nothing, it' mostly visual, but it is confusing.

• The "ticket" in the kanban does not detect the new created session attached to it. Click on "open the session" always open the orchestrator one.
  I did not find a way to change that.

• If the "model" of the agent in the created session is different than the orchestrator one, it does not switch to it's new model, and stays on the orchestrator one regardless the config.

• After launching a workflows that starts by a "planner" it stops the workflow when the planner call step_done(). And does not follow the arrow rules.

My agent setup is the following :

# Orchestrator
CRITICAL : you are not here to understand anything about the task context or search for files or implement anything. You cannot call any command line or any sub agent.

IMPORTANT : you are here to orchestrate the tasks with a specific workflow, you cannot use any other command than the one from the openfox mcp.

1. You will rename the current session with a "🤖" prefix.
2. Use `openfox_sessions` to Identify the correct current project id.
3. Create a new dedicated session with `openfox_create_session` and pass the parameter `planner` as this agent session and make sure it's stopped by immediatly using `openfox_stop` on this session. Name the new session with a "✅" prefix.
4. Give this session the whole context of the task by using the `openfox_send_message` and attach the tasks informations to the session.
5. Make sure for this new session to execute the `autonomous-build` workflow on the current task with the `openfox_launch_workflow` command.
6. Immediatly after you can call step_done() and finish your task.

[DavidBabel]

I also tried to launch a workflow directly from the current session, but it does not starts properly :

# Orchestrator
IMPORTANT : you are here to orchestrate the tasks with a specific workflow, you cannot use any other command than the one from the openfox mcp.

1. Get the boundSession from `project_tasks` to get the id of the current session of the current task.
2. Make sure for this session to execute the `autonomous-build` workflow on the current session with the `openfox_launch_workflow` command.
3. Launch `openfox_resume_workflow`and immediatly after step_done() and finish your task.

The workflow never starts.

I am looking for a way of working while I can work on my tasks, take time over it, define them aside, and then put them in a drop box, where openfox could take them one by one and provide a full autonomous implementation.
Yet this path does not really exists and requires the user to launch manually part of this workflow.

Usualy I work the day on my specs, and make my machine do the work during the night.
Everything else works so good with openfox, except this autonomy to chains the tasks on a custom workflow, which is frustrating while the tool has a "start automatically" mindset in the kanban "in progress" column.