cd /news/ai-agents/a-mac-workspace-where-your-files-and… · home › topics › ai-agents › article
[ARTICLE · art-174326] src=dev.to ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

A Mac workspace where your files and your AI agents sit side by side

A developer released JoeBro, a free, open-source GPLv3 Mac workspace that opens documents and code beside a chat window so AI agents such as Claude Code, Codex and OpenCode can read and edit the same files the user works on. The app binds a folder to a workspace, exposes list, read, create and edit file tools inside it, and holds agent edits as pending diffs when a file is open, with chats and per-project memory stored locally in SQLite over MCP with no account or telemetry.

key takeaway

JoeBro holds agent edits as pending diffs when a file is open and maps invented parameter names like file, filepath and file_name to path so malformed tool calls don't cost a turn.

by read2 min views1 publishedNov 22, 2026

Most AI tools make you copy text out of a chat window and paste it into the place you actually work. I wanted the opposite: my files open and editable in one window, with the agents working on them right beside me.

Short answer: JoeBro is a free, open-source Mac workspace for your AI agents. Documents and code open next to the conversation, you edit them yourself, and the agents (Claude Code, Codex and OpenCode, plus any model you point it at) read and change the same files. This post is about the design decisions behind the file editing, since "let an AI edit my files" is where most of the risk is.

The editor opens documents beside the chat, so you and the model work on the same text. It handles Markdown with a live outline for jumping around long documents, and it also opens Word .doc and .docx files and spreadsheets. You bind a folder to a workspace, and the agent's file tools (list, read, create, edit) work inside that folder.

Three rules, in order of how often they matter:

Models rewrite long files badly in one go. Two practical fixes in the file tools:

There is also a small alias table for the parameter names that models invent (file, filepath and file_name all mean path; old_string means find), because dropping those calls costs a whole turn.

Claude Code, Codex and OpenCode run in their own terminals. JoeBro shows their sessions in the same window as your files, so you can read what they are doing, answer their permission prompts, and see the files they change, from the Mac or from the iPhone app. They also share one per-project memory over MCP.

Whether "held as a pending diff when the file is open" is the right default for files that aren't open yet. Today those go through the approval prompt where there is one, and I keep going back and forth on whether to open the file in the editor automatically instead.

JoeBro is GPLv3, free and local first: chats and memory live in a SQLite file, with no account and no telemetry. One-line install (macOS 26+), which also plugs it into Claude Code, Codex and OpenCode:

curl -fsSL https://joebro.pages.dev/install.sh | bash

Code: https://github.com/joexk1/JoeBro . Short answers to common questions: https://joebro.pages.dev/faq/

── more in #ai-agents 4 stories · sorted by recency
── more on @joebro 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/a-mac-workspace-wher…] indexed:0 read:2min 2026-11-22 · —