Tisty 1.0.4
Connecting an assistant meant copying a block of JSON into a file you first had
to know the name and the whereabouts of. The Agents tab now lists the assistants
already installed on this computer — Claude Code, Claude Desktop with Cowork
behind it, Codex, Antigravity, VS Code, Cursor, Windsurf — and connects the one
you pick.
It writes a single line into that assistant's own settings and leaves the rest
of that file exactly where it was. The row names the file it is about to touch,
so «Connect» is something you can go and check afterwards, and what was there is
kept beside it ending in .before-tisty. A file written in a way Tisty cannot
change without spoiling it — a server declared inline, a key that is not what it
should be — is refused with the lines to paste by hand rather than guessed at.
Nothing is found by asking your PATH: an assistant is known by the settings file
it keeps, because a command can be installed and still not be on it.
A row also says when a connection points at a copy of Tisty that is no longer
there. That failed in silence until now — the assistant simply never got an
answer. Pointing it here again is one click, and so is taking it back out.
Underneath, a fault that shipped in 1.0. Installed from the Microsoft Store, the
configuration Tisty handed you to paste named the window rather than the command:
Windows does not mind the case, and inside that package the window is called
Tisty.exe while the command sits elsewhere. An assistant given that opens a
window and waits for an answer that never comes. That copy now hands out the
name its execution alias answers to, which has the further virtue of surviving
every update, where a path into the package would not.
Two things this does not claim. It never says an assistant is running: it reports
what a settings file says, which is a claim it can keep. And the program you
connected may write its own settings back as it closes, so the row asks you to
close it and open it again — and if the line went with it, the row says «Connect»
again rather than pretending otherwise.
The number stays in the 1.0 line, as it will until the door opened in 1.0.0
works the way it was announced.
Full Changelog: v1.0.3...v1.0.4