-# WRITTEN BY AI! (just the readme only some of the code is ai) A lightweight, slightly chaotic Windows shell replacement / overlay UI experiment.
It is not polished. It is not stable. It does things.
This project was built more as a UI experiment than a production shell replacement.
Expect:
- weird behavior
- hidden shortcuts
- things that only work if you click the “right wrong” spot
- hardcoded shortcuts that may or may not make sense
A custom shell-style interface layered over Windows with:
- Taskbar-like bottom panel
- Clickable system widgets
- Hidden interaction toggles
- Custom app shortcuts (some hardcoded)
⌨️ Hidden / Special Controls
Ctrl + Shift + Caps Lock→ toggles clickability for certain UI elements
- Clicking the clock/time toggles or enables extra interactions (debug-style unlock behavior)
- Clicking temperature:
- toggles weather display OFF for privacy mode
- Does NOT directly open Discord by default
- Requires configuration (see below)
Clicking the settings icon opens the configuration panel.
- Format:
"<id>, <id>, <id>" - Comma-separated Discord channel IDs used for integrations or widgets
- Set:
- Latitude
- Longitude
- Used for weather widget location targeting
- Enables censorship of console/log output for a given username
- Used for demo-safe recordings
Default:
%localappdata%\discord\Update.exe
- Can be changed to any executable path
- Used for launching Discord via the shell shortcut system
Windowsshell requires an environment variable to be set:
TOKEN = <Discord Bot Token>
- This must be a valid Discord bot token
- Used for Discord-related integrations/features
- If missing or invalid, Discord features will fail silently or behave unpredictably
- Discord launcher icon is not guaranteed to work unless configured correctly
- Some integrations assume Windows environment variables exist
- Termius is currently hardcoded into launcher behavior
- You can replace it by changing:
- icon
- executable path
- launcher binding
- You can replace it by changing:
Honestly:
I don’t fully know how you’re compiling this either.
But in theory, it depends on what this evolved from:
its c# so probably something like dotnet build but i have no clue lol (visual studio is nice like that)
Windowsshell is not meant to replace Windows Explorer in a serious way.
It is:
- a sandbox UI layer
- a customizable shell experiment
- a “what if Windows but I controlled everything” project
- If something doesn’t respond → try unlocking click mode:
Ctrl + Shift + Caps Lock - If Discord doesn’t open → check the path in settings
- If weather seems wrong → verify lat/long
- If something feels hardcoded → it probably is
- proper plugin system
- draggable widgets
- real taskbar process binding
- configurable hotkey system
- less hardcoding (optional)
- more chaos (definitely optional)
This shell is basically:
“Windows, but I wanted to see what breaks if I touch everything.”
Use it, break it, rebuild it, or replace it.
Good luck.