Hey everyone. I’ve been running Claude Code as my daily driver and wanted it to do more. Background jobs, Slack integration, multi-agent teams, a web UI. So I built a thin gateway daemon on top of the CLI. The key insight: Claude Code CLI already handles tool use, file editing, memory ( with Auto Memory ), multi-step reasoning. Why reimplement any of that? Instead, I built a thin orchestration layer on top that adds what the CLI doesn’t have natively. What it does: • Wraps Claude Code CLI (and optionally Codex) as engines • AI org system - define employees as YAML files with departments, ranks, managers. They delegate to each other. • Cron scheduling - hot-reloadable background jobs (daily standups, content pipelines, inbox monitoring) • Slack connector - thread-aware message routing with reaction-based workflows • Web dashboard - chat UI, org map, kanban boards, cost tracking, cron visualizer • Skills system - markdown playbooks that Claude Code follows natively • Self-modification - agents can edit their own config, skills, and org structure at runtime with hot reload out of the box • Multi-instance - run multiple isolated instances side by side Max plan compatibility: Since it delegates to the official claude CLI binary, it works with your Max subscription. It does NOT use the Anthropic API or Agent SDK. It literally spawns claude as a subprocess. Same as if you ran the command yourself. No ToS issues. It’s called Jinn : https://github.com/hristo2612/jinn submitted by /u/TotalGod
Originally posted by u/TotalGod on r/ClaudeCode