Device Name
Version
—
Font Size
11
12
13
14
16
18
Grid Columns
Auto
2
3
4
Hover preview
Off
After 1s
After 1.5s
After 2s
After 3s
Device label
In the title bar
In the preview (lower right)
Don't show
Sessions from different devices will look identical on the grid. Grouped view and the sidebar still show device headers.
Activity indicator
Dot + Glow
Glow only
Dot only
None
No user-created views yet. Use the dropdown in the header to create one.
View rule configuration errors
These match_names patterns in ~/.config/muxplex/settings.json were rejected and are excluded from matching -- the view still shows its pins and any other valid patterns. Fix the pattern named above, then reopen this tab to confirm.
Command template
{name} is replaced with the session name. These run shell commands on the server, so the browser can show them but never change them — use the Duplicate action below, or edit ~/.config/muxplex/settings.json directly.
Kill session command
{name} is replaced with the session name. These run shell commands on the server, so the browser can show them but never change them — use the Duplicate action below, or edit ~/.config/muxplex/settings.json directly.
Command pairs
Each pair is a create command and its matching kill command; the pair a session was created with is the one used to delete it. These run shell commands on the server, so the browser composes changes and your shell applies them — Duplicate an existing pair, then paste the generated muxplex commands add line into any shell, including the terminal in this app.
Command pair configuration errors
These entries in ~/.config/muxplex/settings.json were rejected and are not available. Sessions created with them cannot be deleted until they are fixed — see the entry above matching the id named in a delete error, fix it, then reopen this tab to confirm.
Terminal setup
—
Matches this terminal's colors to the dashboard and makes copy/paste easier.
Not installed on this machine yet. Run muxplex tmux install in a terminal here to enable it.
Theme
Generated config file
Show the generated config
Sending a message
This choice is remembered on this device only. Your other devices keep their own.
Model provider API key
Checking...
A key set in the service's environment file is taking precedence. Changes made here will have no effect until it is removed.
Where your conversations are stored
Every conversation with the Agent is written to disk, in full and word for
word, by the agent service — on the machine running that service, which
is not this device. Nothing is deleted on a schedule.
Each conversation becomes a folder under the agent service's own state
directory, .amplifier-agent/state/workspaces/<workspace>/sessions/<conversation-id>/,
holding transcript.jsonl (the messages), a .backup copy,
and metadata.json. The files are readable only by the account the
agent service runs as.
Worth knowing: when the Agent reads one of your terminals, what it read is
part of the conversation — so those transcripts can contain terminal
scrollback, which is usually the most sensitive thing here.
Amplifier Agent