engineering / agent

Director

A macOS tool for supervising coding agents in bb or cmux.

At a glance

Purpose
A macOS tool for supervising coding agents in bb or cmux.
Runs in
Local agent with shell
Operating systems
macOS
Needs
Runtime: Python 3.9+ and bb or cmux; Needs internet: Not stated; Needs accounts or API keys beyond your agent: Not stated
Files and data
Reads files: Not stated; Writes files: Yes; Sends data to other services: Not stated
Tool type
Agent
Delivery
From GitHub
Version
Latest on the main branch
Access
Code on GitHub
Compatibility
According to the README, Director runs on macOS with Python 3.9 or newer and works with bb or cmux using an authenticated agent provider. The README does not name specific agent providers.
External costs
The repository is MIT-licensed and states no pricing. The README requires an authenticated agent provider in bb or cmux. The model provider you connect may charge for usage.
Permissions
The README's installer downloads install.sh and executes it through sh. The README says setup chooses the app and authenticated agent provider, creates starter rules under ~/.local/share/director/profile/ and starts Director. The README says the provider may ask for folder trust or sign-in. The README says Director reviews stopped agents, shows proposed messages or prompt responses, and asks for approval before acting. The README describes watching one app at a time and requiring a separate instruction for recurring scans. The README says cmux hooks setup makes watched agents report their state. The README describes local profile and history writes and an uninstall --purge command that removes personal data.
Usage terms
MIT License, as stated in the repository. See its LICENSE file for the exact terms.

Code on GitHub

vectal-labs/director

MIT

Python22 stars3 forksLast pushed 11 Sept 2026 UTC

keeps your agents running

Public GitHub data fetched · 0 days old

Skill folders in this repository (3)

Folders that contain a SKILL.md file, from GitHub's file list on .

View on GitHub ↗

What it does

Director is a tool for coding agents running in bb or cmux. The README says Director reviews stopped agents and asks for approval before acting. The README says proposed messages or prompt responses are shown before sending.

The README says setup chooses an app and agent, creates starter rules and starts Director. The README describes scan or next as review requests, recurring scans as requiring a separate instruction, and monitoring one app at a time. The README says teaching is stored in a gitignored profile folder and reviews and runtime history in a gitignored state folder.

The source metadata lists install.sh, ROLE.md, director, scripts, templates, tests and docs entries, plus director-bb, director-cmux and director-teachings skill folders.

Who it is for

People who run coding agents in bb or cmux on macOS and want to approve each action Director proposes.

Example tasks

Run director start to start Director.
Say scan or next when you want a review.
Review the rules in ~/.local/share/director/profile/ before approving actions.
Run cmux hooks setup so watched agents report their state.
Run director update to update Director.

Getting started

The README gives a single curl command that downloads install.sh from the repository and pipes it to sh. The README says setup chooses your app and agent, creates starter rules and starts Director. The README also lists director start, director update, director uninstall and director uninstall --purge. To work from source, it says to clone the repository, run python3 director/setup.py --app bb (or cmux), then tell your agent: 'Read ROLE.md and be the Director.' The README has the exact commands.

Limitations

According to the README, Director requires macOS, Python 3.9 or newer, and bb or cmux with an authenticated agent provider. The README says no Python packages need installing and your provider may ask you to trust the folder or sign in. The README instructs cmux users to run cmux hooks setup so watched agents report their state. The README says Director watches one app at a time, the one it was launched in, and recurring scans require a separate instruction. The README does not describe what bb and cmux are. The repository can change at any time; check its README before you install.

Data practices

The README says your rules stay local. The README says teaching is saved in a gitignored profile folder, reviews and runtime history are saved in a gitignored state folder, and each teammate keeps their own history. The README does not describe telemetry. What is sent where depends on the agent provider you authenticate.

Community experience

Not rated yet

Sign in to share your experience.

Comments 0

No comments yet.

Sign in to comment

Report a listing concern