---
title: Philosophy
description: The product principles behind PonyMux—a calm, lightweight home for terminal-based agent work.
---

Coding agents have changed what lives inside a terminal. What used to be a
place for short-lived commands now holds work that may run for hours, pause for
days, and still matter months later.

PonyMux gives that work a home without turning the terminal into an all-in-one
development platform. It should leave you with less to manage than before: the
same tools, the same freedom, and a calmer way to return to the work that
matters.

## Sessions are work records

An agent session is not a disposable process. It has a purpose, a history, and
context worth returning to.

PonyMux treats sessions as durable work records. They should be easy to
recognize, organize, revisit, resume, and fork. Closing a window should not
erase the shape of the work or force you to reconstruct why it existed.

This changes the basic unit of a terminal mux. A session is not merely a
rectangle that happens to be open. It is something you may want to find and
continue long after it leaves the screen.

## Enhance, don't replace

PonyMux should improve the tools you already use, not replace them with a new
layer of abstractions.

Claude Code and Codex remain themselves. Their own terminal interfaces remain
the interfaces. PonyMux does not repackage them as proprietary chat windows or
require them to run inside a prescribed agent workflow.

The same is true of how work is organized. Terminal, session, list, and folder
are familiar, flexible concepts. A Terminal does not have to map to one
project, repository, worktree, or task. It can run an agent, switch sessions,
return to a shell, or open a completely different terminal application. The
structure should adapt to the work, not make the work adapt to the structure.

There should be as little adoption cost as possible: no migration before you
can begin, no new project model to maintain, and no workflow that only makes
sense inside PonyMux.

**Keep the tools. Improve the surroundings.**

## Manage attention, not screen space

More agent sessions do not need to mean more terminal panes on screen.

Agents are long-lived and asynchronous. Most of the time, watching one produce
text is not useful. What matters is knowing when a session needs you, what it
was doing, and whether you can return without rebuilding its context.

PonyMux keeps one Terminal in focus and makes the rest easy to find. Lists,
status, and notifications should direct attention when it is needed, then get
out of the way. They should not create another dashboard that needs to be
watched.

This is why PonyMux does not have split panes. It is not an unfinished layout
feature. It is a boundary that keeps simultaneous work from becoming
simultaneous distraction.

**Run more sessions without looking at more terminals.**

## Serious work should still feel alive

Working with several agents can increase output, but it can also make the day
feel faster, heavier, and more mechanical. A serious tool does not have to add
to that tension.

Pets, themes, shaders, and reactions bring companionship, personality, and
small moments of celebration into the workspace. They do not change the code
an agent writes, but they can change how the work feels while it is happening.

Delight is not the opposite of focus. Used with restraint, it can make a calm
space feel personal without adding another workflow to learn.

## Stay small

PonyMux is about terminals and session management. That focus is a feature.

Project management, issue tracking, long-term memory, orchestration,
collaboration, and data sharing are each large product categories of their own.
Pulling all of them into PonyMux would not complete the product. It would turn
it into a system users have to manage.

We should be willing to say no, even to useful ideas. A feature belongs in
PonyMux when it makes terminal sessions easier to find, understand, continue,
or enjoy. Otherwise, it probably belongs somewhere else.

This does not mean the product should feel bare. It means keeping the model
small while leaving room for expression.

**Simple at the center, personal at the edges.**

PonyMux is not trying to define the future of software development. It is
trying to make one part of it feel lighter: one Terminal in front of you, the
rest easy to return to, and less machinery competing for your attention.