Not built, or not proven yet
Said plainly, so nothing here is a surprise:
- Codex is not part of this version. Its code is kept and tested, but it is switched off: no page, command or provider kind offers it.
- OpenCode's sessions are not reopened after a restart; Restore brings back Claude Code's terminal sessions only. Tia cannot continue an earlier OpenCode conversation by its id; she can only continue the folder's newest one.
- Restore can bring back a terminal a chat took over: when the dashboard ends within about 20 seconds of Continue here in a chat, Restore reopens the terminal on that conversation after the restart.
- Other computers report Claude Code's version only, not OpenCode's, on the Computers page.
- Not seen from a real model: OpenCode's own question forms (the page has them; a real model never asked one in the tests).
- The last checks of this version ran on stand-ins for the coding tools (small programs that answer the way Claude Code and OpenCode do), not on real Claude Code or real OpenCode. The one exception: what the page's Allow in a terminal session looks for was checked against screens recorded from real Claude Code 2.1.326; a later Claude Code that draws its permission dialog another way gets no answer from the page (it sends you to the terminal).
- Work is not finished: plans and planning with AI, repeating tasks, the Automations page folded into Work, a
session on a branch of its own for Do it, Tia's tools for Work, and a token and webhooks for other programs
are not built. The sessions that need an OK are on the dashboard's Today only, not in
hoprig tasks. - What Hoprig's folder check cannot see (Hoprig stays inside each entry's own folder of the workspace): a folder that a program already running on this computer swaps for a link in the instant between the check and the act, and a bind mount, which looks like a folder.
- Files on the desktop: dragging between two Files windows is not built.
- A submodule's own changes are not counted in the repository around it: Source Control and the project counts read git without looking inside a submodule's files (its own settings could start programs). A submodule with uncommitted changes shows them when you open it as its own folder; a new commit in it still shows in the parent.
- Run only on Linux: everything new since 0.2 (the chat, OpenCode, the editor, the desktop, the public
link switch, Updates, one process per conversation, the start of a terminal session by its start file, the text
typed only for a coding tool in front, the ending of a terminal's programs before it closes, the safe git reads),
and everything new in 0.3 (Work and Do it, the New session popup, the App's title bar, session menu and session
rail,
hoprig getand its folder rule, groups, naming rules and a group's own command, the folder check andhoprig workspace mylink, a gateway of your own, the page's answers in a terminal session and the rule of bypass mode). It was not run on macOS or Windows; written for macOS and not run there: the refusal of a gateway program in a folder that Homebrew lets other users change. How Hoprig tells that a process is still the one it started (a process id can belong to another program after a restart of the computer) is exact on Linux; on macOS and Windows it is written and tested with recorded answers of the system only. - Two gaps around one process per conversation: pressing Ctrl+C in a new terminal session before its shell has
read the start line leaves the conversation shown as running there until you choose Continue here or that
terminal ends (its unused start file is removed after ten minutes). A
hoplauncher that is killed hard while its coding tool goes on leaves that coding tool unseen by Hoprig. - On Windows, a second temporary address of the public link whose file names no process identity (one an earlier version started) cannot be stopped by Hoprig: it says so, and that helper is ended by hand.
- Not proven on real devices: a phone's on-screen keyboard in the editor and the chat; changing the Claude account of a provider from the page end to end with a real account; a real stop or restart of a service from the desktop.