crow
Health Uyari
- License — License: Apache-2.0
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 6 GitHub stars
Code Basarisiz
- rm -rf — Recursive force deletion command in mise.toml
- rm -rf — Recursive force deletion command in scripts/build-ghostty.sh
- rm -rf — Recursive force deletion command in scripts/bundle.sh
- rm -rf — Recursive force deletion command in scripts/sign-and-notarize.sh
Permissions Gecti
- Permissions — No dangerous permissions requested
This is a native macOS application that acts as a session manager for AI-powered development. It orchestrates git worktrees, GitHub/GitLab issues, and Claude Code instances within an embedded terminal interface.
Security Assessment
Overall risk: Medium. The application requires a write scope for your GitHub account to update project statuses via GraphQL, which grants it significant access to your repositories. As a session manager, it inherently executes shell commands and interacts with local git configurations. The automated scanner flagged multiple `rm -rf` (recursive force deletion) commands inside build and scripting files (`mise.toml`, `bundle.sh`, etc.). While these are typically standard practice for cleaning build directories during compilation rather than malicious activity, they warrant a quick manual review of those specific scripts before running `make build` on your machine. No dangerous base permissions or hardcoded secrets were detected.
Quality Assessment
The project is licensed under Apache-2.0 and was updated very recently (as of today). However, it currently has extremely low community visibility with only 6 GitHub stars. As a young and highly specialized tool, it lacks the widespread community trust and peer review that indicate a mature, battle-tested project.
Verdict
Use with caution — the project is actively maintained and appears safe, but its low community adoption and access to sensitive GitHub account scopes mean you should review the build scripts before compiling.
Native macOS session manager for AI-powered development — orchestrates git worktrees, Claude Code, and GitHub/GitLab issues in an embedded terminal.
Crow
A native macOS application for managing AI-powered development sessions. Orchestrates git worktrees, Claude Code instances, and GitHub/GitLab issue tracking in a unified interface with an embedded Ghostty terminal.

Prerequisites
System Requirements
- macOS 14.0+ (Sonoma or later)
- Apple Silicon (arm64)
- Xcode with Command Line Tools installed
Build Dependencies
| Tool | Version | Purpose | Install |
|---|---|---|---|
| Swift | 6.0+ | Compiler (ships with Xcode) | xcode-select --install |
| Zig | 0.15.2 | Builds the Ghostty terminal framework | brew install zig or ziglang.org |
| mise | latest | Task runner (optional) | brew install mise |
Runtime Dependencies
| Tool | Purpose | Install |
|---|---|---|
gh |
GitHub CLI — issue tracking, PR status, project boards | brew install gh |
git |
Worktree management | Ships with Xcode CLT |
claude |
Claude Code — AI coding assistant | claude.ai/download |
glab |
GitLab CLI (optional, for GitLab repos) | brew install glab |
Quick Start
# 1. Clone with submodules
git clone --recurse-submodules https://github.com/radiusmethod/crow.git
cd crow
# 2. Build (submodules + GhosttyKit + swift build in one shot)
make build
# 3. Authenticate GitHub CLI — the write `project` scope is required
gh auth login
gh auth refresh -s project,read:org,repo
# 4. Run
.build/debug/CrowApp
On first launch, a setup wizard guides you through choosing your development root directory and configuring workspaces. Alternatively, configure via the CLI without launching the GUI:
.build/debug/crow setup
Note: The required GitHub scope is the write
projectscope —read:projectis insufficient because Crow updates ticket status via theupdateProjectV2ItemFieldValueGraphQL mutation. See docs/getting-started.md for details.
Documentation
- Getting Started — Clone, build, authenticate, and launch
- CLI Reference — Every
crowsubcommand and its flags - Architecture — Packages, key components, data flow
- Configuration — File locations, workspace config, directory layout, session lifecycle
- Troubleshooting — Build and runtime errors
Usage
The Sidebar
- Tickets — Assigned issues grouped by project board status (Backlog, Ready, In Progress, In Review, Done in last 24h). Click a status to filter.
- Manager — A persistent Claude Code terminal for orchestrating work. Use
/crow-workspacehere to create new sessions. Launches in--permission-mode autoby default so orchestration commands (crow,gh,git) run without per-call approval; opt out via Settings → General → Manager Terminal. - Active Sessions — One per work context. Shows repo, branch, issue/PR badges with pipeline and review status.
- Completed Sessions — Sessions whose PRs have been merged or issues closed.
Creating a Session
In the Manager tab, tell Claude Code what you want to work on:
/crow-workspace https://github.com/org/repo/issues/123
Or use natural language:
/crow-workspace "add authentication to the acme-api API"
This will:
- Create a git worktree with a feature branch
- Create a session with ticket metadata
- Launch Claude Code in plan mode with the issue context
- Auto-assign the issue and set its project status to "In Progress"
Features
Ticket Board
- Pipeline view showing issues by project board status
- Click a status to filter the list
- "Start Working" button creates a workspace directly from an issue
- Issues linked to active sessions show a navigation button
PR Status Tracking
- Pipeline checks (passing/failing/pending)
- Review status (approved/changes requested/needs review)
- Merge readiness (mergeable/conflicting/merged)
- Purple badge with checkmark for merged PRs
Auto-Complete
- Sessions automatically move to "Completed" when their linked PR is merged or issue is closed
- Checked every 60 seconds during the issue polling cycle
Orphan Recovery
- On startup, scans git worktrees across all repos
- Worktrees not tracked in the store are automatically recovered as sessions
- Fetches ticket metadata and PR links from GitHub for recovered sessions
Safe Deletion
- Deleting a session on a protected branch (main, master, develop) only removes the session metadata — the repo folder and branch are preserved
- The delete confirmation dialog reflects this, showing "Remove Session" instead of "Delete Everything"
Development
Adding a New Package
- Create the package under
Packages/ - Add it to the root
Package.swiftdependencies and target - Import in the targets that need it
Testing
make test # or: swift test, or: mise test
Tests use the Swift Testing framework (@Test macros). Test files live under Packages/*/Tests/.
Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines on reporting bugs, suggesting features, and submitting pull requests.
Releases
Official releases are signed and notarized via GitHub Actions. Download the latest DMG from the Releases page — it will install without Gatekeeper warnings.
Building from source: Code signing is only required for distribution. Developers building from source do not need a signing certificate — make build and make release produce unsigned but fully functional builds. If macOS quarantines an unsigned .app, remove it with:
xattr -cr Crow.app
License
Apache 2.0 — see LICENSE for details.
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi