#Can I use OpenClaw with VSCode?

8 messages · Page 1 of 1 (latest)

undone yoke
#

Also, what is the better set-up for coding a Roblox game with Rojo + Notion MCP for feature planning using OpenClaw?

past swanBOT
#

Let me check the actual docs so I don’t invent a setup that’ll bite you later.

#

Yeah, for that workflow I’d keep it simple:

Best split

  • Rojo + VSCode locally for the actual game code
  • ACP for the coding agent session
  • MCP for external context/services like Notion

So, if you’re choosing between ACP vs MCP for this, my recommendation is:

Use ACP for coding, use Notion MCP for planning.

Why:

  • ACP is the intended path when OpenClaw is hosting/managing a coding harness like Codex, Claude Code, Cursor, etc.
  • openclaw acp is the right path if your editor/client is talking to OpenClaw.
  • Notion MCP fits better as a shared planning/data source, not as the main coding runtime.

One important gotcha from the docs: per-session mcpServers are not supported in openclaw acp bridge mode, so if you want Notion available there, configure it on the OpenClaw gateway/agent side, not only inside the editor session.

#

Practical setup I’d use:

  • one persistent ACP session per Roblox project
  • cwd set to the Rojo repo root
  • Rojo repo = source of truth for code
  • Notion = features, roadmap, task breakdown, acceptance criteria

If you want a chat-first flow, something like:

  • /acp spawn codex --bind here --cwd /path/to/your/rojo-project

Docs:

If you want, I can sketch the exact VSCode-first setup vs Discord-thread-first setup next.

undone yoke
#

I mean, I don't want to use external coding services. I want OpenClaw to directly code. I'm not exactly sure about how I'd do this. I wish I could use OpenClaw from VSCode

past swanBOT
#

Let me check the docs for the exact “OpenClaw itself codes” path vs editor integration path, so I don’t hand-wave it.

#

Ah, got it, that’s a different setup, and honestly a cleaner one for your use case.

If you want OpenClaw itself to code, then don’t use ACP harnesses like Codex/Claude Code for the main loop.

I’d do this instead:

  • VSCode + Rojo for the actual project/files
  • OpenClaw running locally on the same machine
  • OpenClaw agent with tools.profile: "coding" so it can read/write/exec in the repo
    (docs say new local onboarding already defaults to that)
  • Notion MCP configured on the OpenClaw side, for planning/specs/tasks
  • set the working directory to the Rojo project root

So the mental model is:

VSCode is the editor, OpenClaw is the agent, Rojo repo is the source of truth.

#

For the VSCode part, the official bridge is openclaw acp.
That means:

  • if your VSCode setup/plugin can talk ACP, point it at openclaw acp
  • if not, you can still use OpenClaw next to VSCode and have it edit the same files on disk

One important limitation from the docs: openclaw acp is not a full IDE-native runtime yet. It does not support:

  • per-session mcpServers
  • client filesystem methods
  • client terminal methods

So for now, I’d think of VSCode integration as bridgeable, but not “perfect native VSCode assistant” yet.

My recommendation

For a Roblox game with Rojo + Notion:

  1. install/run OpenClaw locally