vitorgalvao/custom-alfred-iterm-scripts

AppleScript for iTerm2 Alfred integration.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 30 minutes ago
Type:Configuration / DotfilesCategory(s):Editors & IDEsTerminal, Shell & TUIDeveloper Tools
Added to GitGenius on September 18th, 2026
Created on July 31st, 2015
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 433
Total Stargazers: 3,796 (+0)
Total Subscribers: 84 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.2 hours
Mean response time: 3.2 hours
90th percentile: 3.2 hours
Tracked items: 1

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Custom Alfred iTerm Scripts is an AppleScript that integrates iTerm2 with Alfred's terminal features.

The project solves the problem of customizing how Alfred launches commands in iTerm2. Alfred includes built-in terminal integration, but this script provides an alternative implementation that allows users to modify the behavior through editable properties at the top of the script. The approach works by replacing Alfred's default terminal handler with a custom AppleScript that can be tailored to individual preferences.

Users who want finer control over how Alfred interacts with iTerm2 should consider this tool. It suits anyone running both Alfred and iTerm2 on macOS who finds the default integration insufficient or wants to adjust specific behaviors. The installation process is straightforward: copy the script contents into Alfred's terminal preferences under the Custom Application setting, then optionally edit the property lines to change how the script behaves.

The project maintains a single focused script file with clear documentation on setup and customization. Development activity shows consistent attention to keeping the implementation current and accessible, with a convenient one-command installation method provided for users who prefer to copy the script directly from the repository.