Documentation / Home

Aphotic-Hypr Wiki

Welcome to the documentation for Aphotic — a Hyprland setup built for four identities at once: developer environment, gaming rig, AI-assisted workflow, and security research box, without losing the minimalist bones it started from.

Aphotic was previously known as Noctis-Hypr. If you see “Noctis” anywhere in an older link, issue, or local clone, it refers to this same project.

What is Aphotic?

Aphotic is a declarative Hyprland dotfiles collection. Instead of one fixed setup, you pick a base profile (minimal or full) and layer on any combination of layers (gaming, dev, ai, exploit and its sublayers) — all resolved from plain TOML data, not hardcoded install-script logic.

The visible layer is a single hand-vendored Quickshell shell that replaces Waybar, Mako, and Rofi and brings its own lock screen: one bar (in five swappable styles), a status notch, one launcher, real notifications, a Command Center dashboard with the Flow resource map, a full-screen Settings control center, and an always-ready AI chat popout — all reskinned live from whatever wallpaper is active, no rebuild or relogin required. The Signal line skin (Settings → Bar) restyles every one of those surfaces, and the Aphotic greeter is the login screen.

Quick Links

Start here

• Why Aphotic — the problem this was built to solve, and why it’s modular
• Getting Started — install and take your first steps
• Installation — full flag reference, updating, uninstalling, the backup system
• Profiles & Layers — what each base profile and layer actually installs
• Proxmox Test VM — try the install in a guest first, with the VM settings that work

Using Aphotic

• Supported Features — the full feature list
• Command Center — the Super+D dashboard overlay, tab by tab
• Bar Styles — the five swappable bar styles, the Full style’s skins including Signal line, per-style options
• Agentic Workflows — every surface where AI activity shows up, how the opt-ins work, what’s collected
• Resource Engine — how Aphotic arbitrates a GPU (or other finite resource) between two competing workloads instead of letting one crash
• Plugin System — the manifest format, capability model, and full plugin roster
• Build a Plugin — a worked tutorial, start to finish
• Theming — how wallpaper-driven color generation works
• Keybindings — every default shortcut
• CLI Reference — every aphotic command
• Advanced Usage — real configurations and workflows

Reference

• Architecture — how the repo is laid out
• Compatibility — what Aphotic does and doesn’t support
• Security — the exploit layer, disclaimers, and what’s actually collected
• Design Principles — the philosophy behind the decisions
• Release Notes — what shipped, by version

Help & contributing

• FAQ — common questions
• Troubleshooting — when something doesn’t work
• Support — how to get help
• Contributing — working on Aphotic itself
• Resources — credits and related projects
• Project Status — where things stand right now

The four identities

See Why Aphotic for the problem that put these four on one desktop in the first place.

• Developer — the dev layer (Neovim, tmux, fzf, ripgrep, fd, lazygit, GitHub CLI), the launcher’s @ project-switcher mode, and VS Code with live wallust theming (in the full profile).
• Gaming — the gaming layer (GameMode, MangoHud, Steam).
• AI-assisted workflow — the ai layer (Ollama, llmfit hardware-aware model recommendations, Claude Code), inference mode that steps the desktop aside while a local model runs, the Command Center’s AI Chat tab and the standalone Intelligence quick-chat popout, both talking to Claude/Ollama/Gemini/ChatGPT behind one interface, plus an optional local Aphotic Assistant on NVIDIA hardware.
• Security research — the exploit layer and its focused sublayers (recon, web, network, passwords, wordlists, reversing, forensics, reporting), gated behind an explicit authorized-use disclaimer. See Security.

Core design ideas

• Declarative, not hardcoded. Package sets live as data (profiles/*.toml), merged at install time — not bash arrays buried in install.sh.
• Composable, not monolithic. One base profile plus any number of layers, deduplicated automatically.
• Safe to run twice. Every install snapshots your existing configs first; your resolved choices are written to aphotic.toml so a re-run doesn’t re-ask the same questions.
• Honest about what it will do. --dry-run prints the entire plan and touches nothing.
• Reversible. ./uninstall.sh restores your most recent backup.

Getting started

git clone https://github.com/T-Crypt/Aphotic-Hypr && cd Aphotic-Hypr
chmod +x install.sh
./install.sh

On a terminal, running with no flags starts the guided setup: four short steps and one summary to accept before anything changes. It installs the newest release. See Getting Started for what happens next, or Installation for the full flag reference.

View public Wiki source ↗