HKUDS/OpenSpace

Hey loicduong! I couldn't find any mention of **Serena** in the OpenSpace docs (e.g., the [README](https://github.com/hkuds/openspace/blob/main/README_CN.md) and other files). So there’s no official integration or guidance on combining the two projects. You could certainly give it a try, but it isn’t documented or supported out‑of‑the‑box.

[build-system]
requires = ["setuptools>=68.0", "wheel"]
build-backend = "setuptools.build_meta"

[project]
name = "openspace"
version = "0.1.0"
description = "OpenSpace"
readme = "README.md"
requires-python = ">=3.12"
license = {text = "MIT"}
authors = [
{name = "OpenSpace Team@HKUDS"}
]

dependencies = [
"litellm>=1.70.0",
"python-dotenv>=1.0.0",
"openai>=1.0.0",
"jsonschema>=4.25.0",
"mcp>=1.0.0",
"anthropic>=0.71.0",
"pillow>=12.0.0",
"numpy>=1.24.0",
"colorama>=0.4.6",
"flask>=3.1.0",
"pyautogui>=0.9.54; sys_platform != 'darwin'",
"pyautogui>=0.9.40,=2.12.0",
"requests>=2.32.0",
]

[project.optional-dependencies]
macos = [
"pyobjc-core>=12.0; sys_platform == 'darwin'",
"pyobjc-framework-cocoa>=12.0; sys_platform == 'darwin'",
"pyobjc-framework-quartz>=12.0; sys_platform == 'darwin'",
"atomacos>=3.2.0; sys_platform == 'darwin'",
]

linux = [
"python-xlib>=0.3...

Thanks for sharing the steps that worked for you on an Apple M2 Pro Mac Mini. Using a project‑local virtual environment and installing the package in editable mode (`pip install -e .`) is a solid approach, especially on macOS where system‑wide Python packages can cause issues. If you ran into any errors before creating the venv, could you provide the error messages or your Python version? Adding these instructions to the quick‑start guide would likely help other users on similar hardware.

Hi, thank you for raising this issue. We take questions about originality and attribution seriously, and we are happy to provide a direct, public response.

**In short: OpenSpace and evolver are fundamentally different projects.** They diverge at the architectural level — evolver is a prompt generator that delegates execution to an external Hand, while OpenSpace is an in-process worker that directly modifies and validates code. This root divergence leads to completely different evolution triggers, processes, and products. Below we provide a detailed explanation.

## 1. OpenSpace's Design Lineage: From Tool-Level to Skill-Level Self-Evolution

OpenSpace did not start from the concept of "self-evolving agents" in the abstract. It grew out of a concrete, traceable engineering path.

In mid-December last year, we released **[AnyTool](https://github.com/HKUDS/AnyTool)**, a grounding agent that serves as a **worker** to complete tasks. AnyTool monitors low-level tool (MCP, GUI, Web, Shell) e...

Thanks for your interest in OpenSpace!

The `openspace-dashboard` command is installed as a Python console script entry point via `pip install -e .`. It looks like this step was missed. Please follow the [Quick Start](https://github.com/HKUDS/OpenSpace#-quick-start) instructions in the README:

```bash
git clone https://github.com/HKUDS/OpenSpace.git && cd OpenSpace
pip install -e .
```

After that, `openspace-dashboard --port 7788` should work.

Feel free to ask if you have any other questions.