Repository navigation
Releases
Helper 1.1.2
Added
- OMP 19 is supported: chat, sends, background jobs and resume work as they did on OMP 18.
- In OMP 19, a form question can be answered from the phone.
- In OpenCode 1.x, the chat shows how full the context is.
Changed
- When you start a new conversation or resume another one in the agent, the chat follows it and starts over with that conversation, as the agent's own screen does.
Fixed
- After a helper restart, the chat of a Claude Code, Codex or Cline session could go back to the conversation the session started with. It now stays on the one you were in.
- In Codex, a conversation from an earlier run that was resumed in the terminal showed in the chat only after its next message, without its history. It now shows at once, with its history.
- In OMP, after resuming a conversation from the phone, the chat stayed on the old one. It now follows the resumed conversation.
- In Copilot CLI, a subagent's steps showed as separate turns, and its answer could show as the turn's reply in place of the agent's own. The steps now stay inside the turn that started them, and the turn ends with the agent's reply.
- In Claude Code, a question with several steps showed as one request per step. It is now one request.
- A session whose agent was restarted while a turn was running stayed on "working". The interrupted turn now ends, and the session shows what the new run does.
- A prompt sent while the agent was still working could be marked as ended without a reply before its own turn had run. It is now judged after its own turn.
- A prompt sent from the phone could show twice in the chat. It now shows once.
Update
Run togo update, or brew upgrade togo for a Homebrew installation.
If Homebrew asks you to trust the formula, run brew trust --formula gettogo/tap/togo, then retry the upgrade.
To install:
curl -fsSL https://togoapp.dev/install.sh | shHelper 1.1.1
Changed
- For a few dialogs the helper can't read from the screen (Copilot CLI's run-command and path-access dialogs, Droid's file-create dialog), the request on the phone is titled as the agent's dialog, without the command line. It can still be answered from the phone.
Fixed
- After
togo updateor a helper restart, the chat of a Copilot CLI, Droid, Cursor CLI or Amp session was empty. It now shows the conversation as it was. - A request waiting for an answer was lost when the helper restarted, so Approve or Deny from an earlier notification did nothing. Open requests are now kept and can still be answered.
- A request could show one command while its buttons acted on another, when a prompt was answered at the desk just before the next one appeared. A request now answers only the prompt it was opened for.
togo updatecould drop approvals and agent events that arrived as the helper was restarting. The helper now saves them before it exits.- In OMP, a subagent's row could show another subagent's steps, appear twice, or turn into a background job that vanished, and this changed between restarts. Each subagent now has one row with its own steps.
- In OMP, a long session could lose its conversation after a helper restart. It now keeps it.
- In OpenCode 2.x, after resuming a conversation from the phone, picking another conversation in the terminal left the chat empty. The chat now shows that conversation.
- In Claude Code, every send was refused with "input line already holds text" while it showed a suggested next prompt. Sends now go through.
- A chat on a long session with busy subagents opened nearly empty, because subagent steps used up the page. A page now holds the asked number of messages from the main conversation.
Update
Run togo update, or brew upgrade togo for a Homebrew installation.
If Homebrew asks you to trust the formula, run brew trust --formula gettogo/tap/togo, then retry the upgrade.
To install:
curl -fsSL https://togoapp.dev/install.sh | shHelper 1.1.0
Added
- Menus an agent draws in its terminal, such as model lists, settings, command lists and pickers, open as native lists in the app, with search where the agent offers it. They are read from the agent's screen, so no agent needs setting up.
- A one-line question from an agent, such as a key or a code, opens as a single field. What you enter isn't shown again.
- The command list in chat includes the agent's own commands, read from the agent.
- In OpenCode, terminal commands appear in the command palette and custom agents appear as modes. You can pick a model variant, connect or disconnect MCP servers, and see background shells in mission control. Undo and redo show in the chat.
- OpenCode forms support required, preset and conditional fields. Provider sign-in shows its address and code in the app, with a button that opens the address on your phone.
- OMP's own screens, such as its resume, model and settings choosers, forms and questions, open as native screens. Typing from the phone waits while one is open.
- In OMP, form questions, pictures in tool results and background jobs show in the app. Effort offers the levels the active model takes, and a setting the project overrides says so.
- The installer makes
togoavailable in a new terminal. Where it can't link from/usr/local/bin, it adds one line to your zsh, bash or fish profile;--no-modify-pathskips that.
Changed
- Mission control lists what is running and what went wrong. An agent or background shell that finishes leaves the list, and one that failed or was stopped stays until your next prompt.
- A command whose result can't be seen is reported as sent instead of done. If its list opens later, the app offers it.
- A newer release of an agent keeps its native chat while its major version is the same.
- File search follows the folder the agent is in and covers folders added to the session.
Fixed
- A session could be reported done, and shown idle, while subagents it had started were still running. It now stays working until the last one finishes.
- Subagents and background jobs could show as running after the agent had exited or the helper had restarted. They now show their real state.
- When an agent moved to another conversation, the chat mixed the old messages with the new ones. The chat now starts over on the new conversation.
- A prompt sent just as the agent moved to another conversation could reach the wrong one or be sent twice. It is now refused or reported, and never sent again.
- An approval answered from the phone could be reported before the agent had taken it. It is now reported once taken; otherwise the request stays open and says the answer wasn't confirmed.
- Two approvals asked back to back with the same wording could be mixed up, so an answer meant for the first reached the second. Each answer now reaches its own request.
- A request left waiting longer than ten minutes could no longer be answered from the phone. It now stays open for as long as the agent is asking.
- A tool finishing could close another tool's pending approval. Each approval now closes only with its own tool.
- A needs-you notification that reached no device was dropped. It is now sent again after 1, 3 and 9 minutes.
- An answer from a notification was lost when the helper couldn't read the terminal for a moment. It is now retried.
- Ordinary reply text, such as a ticket number or a link containing "login", could raise a sign-in request. It no longer does.
- A session whose agent was started again by hand in its pane stayed shown as ended. It now shows as running again.
- Chat stopped updating after a break in the agent's feed until the session was reopened. It now recovers on its own.
- A message starting with a slash word the agent doesn't know failed to send. It is now typed into the agent as text.
- Tool steps containing tabs or control characters were missing from the chat. They now show.
- Typing from the phone was lost when the session's terminal was scrolled back in tmux copy mode. It now reaches the agent.
- The Lock Screen activity could keep an old state after an update failed to send, or stay on "Offline" after the machine was back. It now catches up.
- Ports listed the same port once per worker process and per address, and cut command names short on macOS. Each port now shows once, with its full command name.
- Review showed renamed files, files with unusual names, and files with both staged and unstaged changes incorrectly. They now show as git reports them.
- Tool output could hide ordinary prose after the word "password" and show some real secrets written as lower-case NAME=value. Hiding now follows the shape of the secret.
- On Linux, restarting or updating the helper ended every session. Sessions now keep running, and the helper stays under systemd after a restart.
- On Linux, opening a link from an agent failed after the helper was moved or reinstalled. Links now open.
togo updatecould replace a helper built from source with the older release. It now leaves a newer build alone.togo uninstallleft its background service running. It now stops it.- The installer failed on a Mac with neither minisign nor OpenSSL 3. It now installs there.
- In OpenCode, a prompt sent from the chat after /new or a fork in the terminal went to the conversation you had left. It now goes to the current one.
- In OpenCode, a chat opened after a helper restart showed no earlier messages. It now shows its history.
- In OpenCode 1.x and Kilo, a prompt sent while the agent worked skipped the queue. Queued prompts now go out in order.
- In OpenCode, a picture sent from the phone arrived as a file path. It now arrives as a picture.
- In OpenCode, the resume picker listed archived sessions and found only the newest 50. It now lists live sessions only and searches all of them.
- In OpenCode, one subagent could show as two rows. It now shows once.
- In OMP, the chat stopped updating once OMP started background agents. It now keeps updating, and each background agent shows once under its task name.
- In OMP, a session was reported done while OMP carried on working after one of its own reminders. It now stays working until that work ends.
- In OMP, the session title didn't follow a retitle, and a subagent's title could replace it. The title now follows the conversation.
- In OMP, no replies showed in the chat when OMP's data folder was moved or a profile was used. They now show.
- In OMP, a forked conversation's replies were missing or shown as a subagent's. They now show in the chat.
- In OMP, resuming from the app dropped the options the session was started with. Resume now keeps the model, folders and extensions.
- In OMP, the plan ignored a todo list edited by hand. It now follows the list.
- In Pi, a message sent while the agent worked ended the turn as interrupted, and its tool results never showed. The message now joins the running turn.
- In Pi, the chat and the resume list were empty for a folder whose name holds characters such as [ and ]. They now show.
- In Pi, resuming a session from the app could fail, and unnamed sessions had no title. Resume now works, and an unnamed session is titled by its first message.
- In Kimi, the old plan, subagents and background tasks stayed in mission control after /new. They are now cleared.
- In Kimi, a question or approval could stay open after its turn was cancelled, which also held back later done notifications. It now closes when the turn ends.
- In Kimi, a background task could show as running after it had finished. Its row now closes.
- In Kimi, a turn started by a skill showed the agent answering nothing. The chat now shows its prompt.
- In Kimi, a turn could end early while Kimi went on working in it. It now ends when Kimi does.
- In Goose and Crush, the chat kept the old conversation after Resume, or stayed empty after a restart, until the agent wrote to it. It now moves to the resumed conversation at once.
- In Goose and Crush, a new session could pick up an older conversation of another instance in the same folder. It now follows only a conversation made after it started.
- In Crush, a finished tool could go back to running and then show as interrupted. It now stays finished.
- In Cline, the chat stayed on the old conversation after Resume. It now follows the resumed one at once.
- In Cline, a turn that paused on a permission prompt or a long tool never showed as running again, and its later tools read as interrupted. The turn now reopens when it goes on.
- In Copilot, replies stopped showing after a very large tool result. They now keep showing.
- In Copilot, earlier replies were drawn again as part of the current turn after a helper restart. Each reply now shows once.
- In Droid, Copilot, Cursor and Amp, a failed turn stayed shown as running and its error never appeared. The turn now ends with the error.
- In Droid, an earlier turn's failure could be drawn on a turn that succeeded. Each turn now shows its own outcome.
- In Codex, an approval that offered a policy amendment among its choices never reached the phone. It now does.
- In Codex, the chat could follow the wrong conversation after /new or /resume in the terminal. It now follows the one the terminal is on.
- In Codex, Stop, Compact and model changes could target the wrong conversation or model after /model in the terminal. They now follow the session.
- Codex CLI 0.169 lost its native chat. It works natively again.
- In Claude Code, a stopped subagent ended the main turn as interrupted. Only stopping the main agent ends it now.
- In Claude Code, text, plan rows and file counts could double after the conversation was read again. They now show once.
- In Claude Code, a background agent or shell could stay shown as running after it had finished. Its row now settles.
- In Claude Code, the context meter jumped between two values on sessions with a larger context window. It now follows the agent's own figure.
- In Claude Code, a retry warn...
Helper 1.0.4
Fixed
- New agent sessions could reopen an old conversation. They now start fresh unless you choose a conversation to resume.
- Resumed conversations could replay completed work as new activity. History now loads as one snapshot, with a loading signal before replay begins.
- Earlier chat messages could be skipped when reconnecting. The helper now identifies missing history so the app can retrieve it.
- Live API-backed sessions could lose their connection after a helper restart, including sessions started through symlinked folders. Their endpoint and credentials now recover together.
- Agent updates could lose names, roles and clocks, and current Codex worker activity could go missing. Those details now survive updates and replay.
- Approval requests could arrive as a Live Activity without their question or actions. A normal actionable notification now remains available until the device confirms it saved the request.
- Restart could report failure after the service manager had already replaced the daemon. It now verifies the replacement against the original shutdown request.
- Removing and re-adding a paired relay could interrupt withdrawal of its offline notification. The old connection now drains before its replacement opens.
- Disconnecting while a request waited for input could block RPC shutdown. The connection now closes before waiting requests are canceled.
Update
Run togo update, or brew upgrade togo for a Homebrew installation.
If Homebrew asks you to trust the formula, run brew trust --formula gettogo/tap/togo, then retry the upgrade.
To install:
curl -fsSL https://togoapp.dev/install.sh | shHelper 1.0.3
Fixed
- A session's chat could switch to a conversation of the same agent started outside Togo in the same folder, along with its working state and alerts. This affected OMP, Pi, Kimi, Goose, Crush, Vibe and Cline. Each session now follows only its own agent.
- A Codex started outside Togo in the same folder could send its approvals and alerts to a Togo Codex session. They are now ignored.
- OMP's todo list didn't show in the chat or mission control. It shows again, grouped by phase.
- In OMP, /resume and /new in the terminal didn't move the chat to the new conversation. The chat now follows within a couple of seconds.
- After the helper restarted, an open chat could show "Nothing said yet" until you left and came back. It now shows the whole conversation.
Changed
- A todo list the helper can't read shows as a tool step in the chat instead of disappearing.
- In Goose and Crush, a conversation you start inside the agent shows in the chat once the session restarts. This keeps another Goose or Crush in the same folder out of the chat.
SHA256SUMS is signed with minisign, key ID 2499979E76983FAB. The macOS binaries are signed with a Developer ID and notarized by Apple.
Helper 1.0.2
Changed
- Future
togo updatewill also update Homebrew installs by runningbrew upgradefor you, andtogo update --checkworks for them.
Update
If you've already installed: run togo update, or brew upgrade togo if you installed with Homebrew.
New install: pick one.
curl -fsSL https://togoapp.dev/install.sh | shbrew install gettogo/tap/togoSHA256SUMS is signed with minisign, key ID 2499979E76983FAB. The macOS binaries are signed with a Developer ID and notarized by Apple.
Togo v1.0.1
Fixed
- Swiping or dragging in the terminal of a full-screen agent, such as OpenCode, froze the screen until you pressed Esc. Swipes now reach the agent as arrow keys, and drags and double-taps no longer freeze it.
- A two-finger tap in the terminal could open tmux's pane menu, which offers Kill and Respawn. It no longer appears.
- A session whose folder was deleted or moved kept reconnecting. It now connects, and the helper never runs anything for it in a folder you didn't choose.
- After the helper updated itself, its background service could run outside launchd or systemd, so nothing restarted it after a crash until the next login. It now stays under the service manager.
Update
Run togo update on your machine (with Homebrew, brew upgrade togo). New installs:
curl -fsSL https://togoapp.dev/install.sh | shSHA256SUMS is signed with minisign, key ID 2499979E76983FAB. The macOS binaries are signed with a Developer ID and notarized by Apple.
Togo v1.0.0
First release of the Togo helper. It runs on your Mac or Linux machine and connects your coding agents to the Togo app on iPhone, iPad and Apple Watch.
Install
curl -fsSL https://togoapp.dev/install.sh | shThis installs togo to ~/.togo/bin and starts the background service. To skip the service, use sh -s -- --no-service.
Verify
SHA256SUMSis signed with minisign, key ID2499979E76983FAB.- The macOS binaries are signed with a Developer ID and notarized by Apple.
- The Release verify workflow rebuilds the Linux archives from this tag and checks that they match.