Most task servers describe work and stop there; here the same session can read the code, run the tests, drive a browser and then update the task's status and activity log, which is what keeps the graph honest. The priority engine is the unusual part — time decay and effort weighting mean "what's next" moves on its own rather than reflecting the order things were entered. Set the boundaries deliberately: ALLOWED_DIRS and READONLY_MODE are the only things standing between these tools and the rest of the disk, and the browser and AppleScript families need their own prerequisites before they do anything.
An orchestration layer that combines a priority-driven task manager with the tools needed to act on it: file read and write, code search and surgical edits, terminal sessions, Playwright browser control and AppleScript. Filesystem access is bounded by an allowed-directory list and an optional read-only mode.
- Tasks and subtasks with numeric priority, dependencies, status and related files — addTask, addSubtask, listTasks, updateStatus, updateTask, removeTask, getNextTask
- getContext returns one task's full context block including related files and its activity log, and generateTaskFiles materialises a Markdown file per task plus a table overview
- A priority engine you can tune rather than guess at: recalculatePriorities, configureTimeDecay, configureEffortWeighting, getPriorityStatistics, getDependencyAnalysis, plus templates through getPriorityTemplates, suggestPriorityTemplate and addTaskWithTemplate, and quick moves with bumpTaskPriority and deferTaskPriority
- parsePrd turns a product document into tasks, expandTask breaks one open, and reviseTasks folds a change request back into the graph
- A file watcher that keeps the task files and the table in sync — initializeFileWatcher, getFileWatcherStatus, forceSyncTaskFiles
- Filesystem tools inside the allowed directories: read_file, read_multiple_files, write_file, copy_file, move_file, delete_file, create_directory, list_directory, tree, search_files, get_file_info, with list_allowed_directories and get_filesystem_status making the boundary visible
- search_code for retrieval and edit_block for surgical old-block-to-new-block replacements rather than whole-file rewrites
- Terminal orchestration: execute_command, read_output, list_sessions, force_terminate, list_processes and kill_process, with blocked commands and timeouts as guardrails
- Playwright browser control — navigate, click, type, hover, drag, select, press keys, screenshots, accessibility snapshots, PDF save, console messages, network requests, dialogs, file upload, tabs and resizing
- applescript_execute on macOS for the things only the OS can do
No account for the core. Node.js, with the MCP server started as bin/agentic-control-framework-mcp --workspaceRoot pointing at your project; the same code also runs as the acf CLI. WORKSPACE_ROOT sets the default workspace, ALLOWED_DIRS adds directories the file tools may touch, and READONLY_MODE=true disables writes entirely. Browser tools need Playwright browsers installed (npx playwright install), and the AppleScript tool needs macOS. GEMINI_API_KEY is what enables the AI-backed planning tools — parsePrd, expandTask and reviseTasks — and nothing else depends on it.
One command — npx -y agentic-control-framework