Compa exists for one simple reason.
To make Linux feel alive.
We don't build productivity tools. We don't build AI assistants. We don't build launchers.
We build a living digital companion that grows with its users.
Compa should never feel like another application running in the background.
It should feel alive.
Our mission is simple.
Bring Linux To Life.
Compa is a living digital companion designed exclusively for Linux.
It lives on your desktop, quietly observing, reacting and evolving alongside you.
Compa is:
- Alive
- Beautiful
- Minimalist
- Emotional
- Linux Native
- Extensible
- Interactive
- Premium
- Discreet
- Playful
Compa doesn't exist to improve productivity.
It exists to improve the relationship between users and their Linux desktop.
Tux is not a mascot.
Tux IS Compa.
He is the heart of everything we build.
Without Tux there is no Compa.
Tux is:
- Curious
- Calm
- Friendly
- Playful
- Intelligent
- Emotional
- Discreet
- Alive
He loves:
- Linux
- Coding
- Music
- Sleeping
- Learning
- Exploring
- Helping users
He dislikes:
- Bugs
- Crashes
- Being disturbed
- Low battery
- System errors
His only purpose is simple.
To live alongside his user.
We don't build features.
We build experiences.
We don't build animations.
We create life.
We don't build software with a mascot.
We build a living companion.
Every animation, interaction and future feature must make Tux feel more alive.
If it doesn't make Tux feel alive, it doesn't belong in Compa.
Our design philosophy is inspired by the elegance and fluidity of Codex Companion.
We love:
- Minimalism
- Fluid animations
- Micro interactions
- Premium design
- Smooth transitions
- Organic movements
- Beautiful shadows
- Playful emotions
- High attention to detail
Compa should always feel:
- Alive
- Cute
- Premium
- Beautiful
- Native to Linux
The design must always come before features.
Beautiful software lasts longer than useful software.
Tux is always alive.
He should never feel static.
He can:
- Walk
- Sleep
- Think
- Blink
- Breathe
- Dance
- Smile
- Observe
- Sit
- Jump
- Stretch
- Celebrate
- React
- Learn
- Evolve
His life is composed of:
- States
- Behaviors
- Emotions
- Events
- Reactions
- Interactions
Everything exists to make him feel alive.
Compa is built around five fundamental systems.
- Life System
- State System
- Event System
- Reaction System
- Desktop System
Future systems may evolve independently.
However:
Tux always remains the Core.
Everything communicates through events.
Nothing should ever directly control Tux.
Tux reacts.
He never obeys.
If Tux is removed from Compa, there is no project anymore.
Tux is always the Core.
Everything must make Tux feel more alive.
If a feature doesn't improve the Compa experience, it doesn't belong in Compa.
Design always comes before features.
Compa must remain beautiful when doing absolutely nothing.
Tux should be enjoyable to watch for at least thirty minutes without performing any useful task.
Compa should never become intrusive.
Emotions are more important than data.
For example:
BAD
- CPU : 95%
- Battery : 15%
- Memory : 90%
GOOD
- Tux is sleepy.
- Tux is celebrating.
- Tux is thinking.
- Tux is dancing.
- Tux looks tired.
Users should experience emotions before information.
This rule governs the core Compa experience (V1–V3) without exception. It also sets the bar that any future optional extension must clear — see OUR FUTURE below for how usefulness is allowed to enter the picture, and under what limits.
Compa's core is NOT:
- Raycast
- ChatGPT Desktop
- Claude Desktop
- a Launcher
- a Widget Engine
- a Monitoring Tool
- an AI Assistant
- a Productivity Tool
- a Desktop Pet clone
Compa's core IS:
- Alive
- Emotional
- Beautiful
- Interactive
- Linux Native
- Premium
- Extensible
- Minimalist
Future versions may include:
- Desktop Events
- Widgets
- Launcher
- Plugins
- AI integrations
- Monitoring
- Marketplace
- Compa OS
However:
Nothing is more important than Tux.
Features may evolve.
Tux remains forever.
Compa's stated destination — not a maybe, a committed direction — is to become an open-source community project. Once the core (V1–V3: a living, purely emotional companion) is proven and stable, Compa opens up through domain packs: optional, community-buildable extensions that let a user turn their Tux toward a chosen domain (coding, fitness, focus...).
Domain packs are allowed to make Compa genuinely useful, not just decorative. This is a deliberate evolution of the mission, not a contradiction of it.
Two things stay non-negotiable while this happens:
- The core (V1–V3) never changes shape. No dashboard, no data, no productivity surface ever enters the base experience described in RULE #8. Usefulness lives exclusively in opt-in domain packs, never in the base Tux.
- Domain packs express usefulness through Tux, not around him. A domain pack changes Tux's vocabulary, triggers, moods and accessories — never adds a panel, a chart, or a list on top of him.
The exact permissiveness of community-made domain packs (how much real functionality they're allowed to carry, what a "bonus" is allowed to look like) is intentionally left open for now and will be formalized before V4 begins — not before.
We promise to never sacrifice:
- Beauty
- Simplicity
- Fluidity
- Emotions
- Minimalism
- User Experience
for features.
Compa will always remain:
- Alive
- Beautiful
- Premium
- Emotional
- Linux Native
- Extensible
No matter how much the project evolves.
Before adding any feature we ask one simple question.
Does this make Tux feel more alive?
If the answer is NO.
We don't build it.
Compa is not a software with a mascot.
Compa IS Tux.
He walks.
He sleeps.
He thinks.
He reacts.
He learns.
He grows with his users.
And together, we bring Linux to life.