Omahub
← All plugins
S

Agent Term

by skuthus

Drop-down terminal from the top of the screen, running your default Omarchy coding agent. Toggle with the Copilot key or Super + `. Set the key from the terminal.

GitHub

Security review

No obvious issues detected

Deterministic scan — not a security guarantee

None
Risk level
None
Analyzed commit
f6505d5
Scanned
1 month ago

No potentially dangerous behavior detected in the analyzed commit.

Automated analysis only — not a security guarantee.

AI advisory review

Review recommended

Language-model assessment · ~deepseek/deepseek-v4-flash-latest — advisory only

Low
AI risk level
Low
Recommendation
review
Model
~deepseek/deepseek-v4-flash-latest
Analyzed commit
f6505d5
Reviewed
1 month ago

The deterministic scan found no issues, and the plugin is largely transparent: it binds a hotkey, toggles a drop-down terminal, and launches the user's configured Omarchy agent. However, scripts/install-cli runs automatically on plugin load and force-replaces ~/.local/bin/agent-term with a symlink without checking for an existing file, which is a minor destructive behavior. The keybinding changes are documented and expected, but the silent file replacement warrants a human look before publishing.

  • scripts/install-cli is executed automatically from Service.qml and uses ln -sfn, silently replacing any existing ~/.local/bin/agent-term file or symlink.
  • apply-binds.sh unbinds SUPER + grave and SUPER + SHIFT + code:201, potentially overriding user bindings for those keys while the plugin is enabled (documented in the README).
How this check works

This review combines the deterministic scan (the rule-based results above) with an independent look at the plugin's code by a language model. The model reads a trimmed sample of the repository's files, the manifest, and the README, then gives a plain-language risk level and a recommendation: install (no notable danger), review (look closer first), or avoid (clearly dangerous).

It runs on the same analyzed commit as the deterministic scan and is strictly advisory — it is not a security guarantee and never blocks a plugin by itself. A human moderator still reviews plugins before they are listed.

AI advisory only — automated analysis, not a security guarantee.

Install
$ omarchy plugin add https://github.com/skuthus/omarchy-agent-term --enable
Developer Tools #Hyprland #quickshell #ai

Agent Term

Drop-down terminal from the top of the screen, running your default Omarchy coding agent.

Install

omarchy plugin add https://github.com/skuthus/omarchy-agent-term.git --enable

From a local checkout:

./scripts/install-local

That puts agent-term on your PATH (~/.local/bin). After install, add this window rule to ~/.config/hypr/hyprland.lua so the terminal parks as a top panel (skip if it is already there):

o.window("org.omarchy.agent-dropdown", {
  float = true,
  size = { "(monitor_w*0.6)", "(monitor_h*0.55)" },
  move = { "(monitor_w*0.2)", "(monitor_h*0.03)" },
  workspace = "special:ask silent",
  animation = "slidevert",
})

Then hyprctl reload.

Usage

agent-term                 # toggle the drop-down
agent-term hotkey          # show the current key
agent-term hotkey copilot  # Copilot key
agent-term hotkey grave    # Super + `

Copilot is the default. Super + ` gives the Copilot key back to the Omarchy menu. First open launches omarchy agent --inline (your default agent). If none is set, the default-agent picker opens.

Do not also bind those keys in ~/.config/hypr/bindings.lua — the plugin owns them while it is enabled.

Remove

omarchy plugin remove skuthus.agent-term --yes
rm -f ~/.local/bin/agent-term

The Copilot key returns to the Omarchy menu. The window rule in hyprland.lua can stay or be deleted.

License

MIT