Everyday comfort
This page is generated from docs/guide.en.md · Edit this page on GitLab
Objects have an address. A review report, a session and a note page are written #/reviews/216, #/sessions/code/12, #/notes/4: the link can be pasted into a note or a message (“Copy the reference” now gives both links — the forge shows the diff, Mergerie shows the report, the score and the verdict), the browser's Back button returns to the previous object instead of leaving the tool, and an address you receive wins at load time over the tab of your last visit — you open a link to go to that object. Tabs deliberately have no address: every menu click would become a history entry, and Back a “previous tab” nobody asked for. A link to an object that is gone does nothing rather than showing an error page.
The tab, the sub-tab and the Reviews stage are remembered from one session to the next — and nothing else: no search, no dialog, no open report, because a stale state is worse than a clean start · keyboard shortcuts (1-9 then 0 for the ten tabs, / search, n new todo, r fetch MRs, l logs, ? help, Esc closes) · a dynamic favicon during a job · error messages translated into actions (certificate, token, CLI not found, timeout, network — including “Mergerie is not responding” with a Try again button when the server is down) · a five-step start-up assistant (agent, forge — GitLab or GitHub —, repositories, what your team uses, first fetch) as long as the connection and the repositories are not configured, with the steps ticked off as you go, and as long as nothing is configured that is the screen the app opens on (the morning brief takes over from the next day) · every form field carries an i icon whose hover (or keyboard focus) explains what it is for · no counter is shown before its data: a skeleton while it loads, never a “0” that would read as “nothing to review”.
- A window can be set aside instead of lost. Every window you type into carries a
—button in its top-right corner: it minimises to the bottom of the menu, the screen becomes whole again, and you go and check whatever you needed to check — a branch name in Git, a ticket's state in Jira. Clicking its chip brings it back as it was: the fields you filled, the cursor in the field you left, and the tab it started from — that is where its result will show. The chip's cross discards it for good, like Cancel. The button stays in the corner even when the form scrolls, and a window brought back still protects what you typed against a click outside. Windows that ask a question (a confirmation, picking a verifier) have no such button: they keep their caller waiting, and setting one aside would keep it waiting forever. - The menu bar can be arranged (Settings → General). It carries the everyday work by default — Reviews, AI Dev, Agents, Notes, Jira, Stats, Settings — and leaves Git, Docker, Jenkins and Links folded away, one tick from coming back. Then move up what you open ten times a day, hide what you never use: drag and drop or arrows, applied at once. “Restore the original menus” returns to that starting point, folds included. A hidden menu also leaves the palette and the number shortcuts —
3opens the third shown menu, not the third original one; offering a screen whose menu entry has gone would be a one-way ticket. The feature itself stays: nothing is disabled, only filed away. ⚠ Settings cannot be hidden (it is the way back), and the arrangement is remembered in this browser, like the theme — not in the database. The folded menus are also found by use: a door to one of them — “Resolve in Git → Merge” on a conflicting merge request, “See the logs” from the brief, a Jenkins job from a card, “this repository has a compose file: show Docker” on a repository's row — unfolds the menu for good, as if the box had been ticked. The Jenkins sub-tab of Settings follows its menu. - Command palette —
Ctrl/Cmd+K. You type a fragment and jump wherever you want: a tab, a stage, a merge request, a session — the search covers what is already loaded, so it answers without calling the server.?shows the full list of shortcuts. - Browse the list from the keyboard:
j/kmove down and up in the visible list,Enteropens,Escreleases. On the focused card:dthe diff,vverify,cthe context,mmark handled,xtick for a joint verification — each one clicks the RENDERED button, so what is disabled stays disabled. No focus outline appears until you have pressed a key. - Copy instead of retyping. A branch name copies on click everywhere it shows (merge request card, a session's project line, the explorer, the report); Shift-click copies
git fetch origin && git checkout <branch>. A merge request's ⋯ menu carries "Copy the reference" —!217 — 3× payment (8.1/10 · verified) <url>, the message already written. On the Docker side, every service, every log stream and every Make target carries its equivalent command, to copy and continue in a terminal. - The palette opens a reference typed alone:
!217orPROJ-1408go straight there onEnter;⌘/Ctrl+Enteron a merge request opens its diff rather than its report. - The quick capture (
n) understands a short syntax:!217 reread the total @tomorrow !!creates a todo linked to !217, due tomorrow at 9, high priority.@mondayand@12/09work too; anything not recognised stays in the title, as written. - An absolute date carries its "3 hours ago" on hover — session cards, merge requests, Jenkins builds.
- The interface keeps still. A refresh that changes nothing no longer rebuilds the list: the page does not blink while you read it. When a list really does load, its cards arrive in a cascade — once, on load, not on every character typed into a filter.
- What is running is marked on the object that is running: the merge request or the session concerned carries an animated outline, one object at a time. It freezes when the tab goes to the background and stays still if the system asks for reduced motion.
- The log no longer eats the browser: past a few thousand lines, the oldest are pruned and a banner says so.
- The report panel opens on what has changed since your last visit — arrivals, departures, and the one that has been waiting the longest. Three lines at most, and nothing at all when nothing has moved.
- The “resume an existing agent session” field does not behave the same depending on the backend. With claude, sessions are filed per project directory (
~/.claude/projects/…): since Mergerie works in its own clone, an identifier taken from elsewhere — your own repository, a session opened by hand in a terminal — will not be found there. The work then restarts from a fresh session with the context re-injected, and the card says so. With copilot, the identifier is an isolated home path: it resumes from anywhere. The identifiers Mergerie offers (“Resume in terminal”, the session a branch came from) are always in the right directory.
- An out-of-repo coding session carries the “AI output” button at session level, not only on each folder: “what did the AI do?” is what you ask while looking at the card. When the session covers several folders, the view offers a selector to move from one to the next without closing.
- A session covering several projects (coding, exploration, or out-of-repo coding) shows its list folded, with a “Show the N projects” to unfold it. Past a few repositories, a single session otherwise filled the whole screen and hid the others — which are exactly what you came to look at. The folded state is remembered per session: it survives the automatic refreshes.
- Reading a report survives a refresh: the scroll position, the tab and the version you were reading are kept as long as the report itself has not changed.
- An identity line that is too long (project path, author, date) is truncated to the card's width: hover then shows the full text — the tooltip only appears if the text is really cut, and disappears when the window widens. The links to the ticket and to the forge have their own line, where they wrap instead of being cut.