Install Logseq for Knowledge Management

Logseq is an open-source, local-first outliner for notes, tasks, and knowledge graphs. It stores everything as plain Markdown (or Org-mode) files you control, which makes it portable and easy to back up. This guide walks through installing Logseq on Linux via AppImage, setting up your first graph (vault), using daily notes, extending it with plugins, and syncing across devices without paying for Logseq's own sync service.

Install Logseq via AppImage

Logseq ships an AppImage as its official Linux release. AppImages are self-contained — no package manager, no root required.

Download the AppImage

Grab the latest release directly from GitHub. Check github.com/logseq/logseq/releases for the current version number and substitute it below.

wget -P ~/Applications \
  https://github.com/logseq/logseq/releases/download/0.10.9/Logseq-linux-x64-0.10.9.AppImage

Make it executable and run it

chmod +x ~/Applications/Logseq-linux-x64-0.10.9.AppImage
~/Applications/Logseq-linux-x64-0.10.9.AppImage

On first launch, if you see a FUSE-related error, install the FUSE library for your distro:

# Debian / Ubuntu
sudo apt install libfuse2

# Fedora / RHEL family
sudo dnf install fuse-libs

# Arch
sudo pacman -S fuse2

Create a desktop launcher

AppImages do not auto-integrate into your application menu. Use appimaged, or create a .desktop file manually so Logseq appears in your launcher.

mkdir -p ~/.local/share/applications
cat > ~/.local/share/applications/logseq.desktop <<'EOF'
[Desktop Entry]
Name=Logseq
Exec=/home/$USER/Applications/Logseq-linux-x64-0.10.9.AppImage --no-sandbox
Icon=logseq
Type=Application
Categories=Office;Productivity;
Comment=Local-first knowledge base
EOF

The --no-sandbox flag is needed on many distros because the Electron sandbox requires unprivileged user namespaces. On Fedora 40+ and Ubuntu 24.04+ with stricter kernel defaults you may also need:

echo 'kernel.apparmor_restrict_unprivileged_userns = 0' | \
  sudo tee /etc/sysctl.d/99-userns.conf
sudo sysctl --system

Be aware this slightly relaxes a kernel security boundary. Evaluate that trade-off on shared or high-security machines.

Set Up Your First Graph (Vault)

Logseq calls a notes directory a graph. On first launch you are prompted to open or create one.

1. Click Add a graph and choose a folder — for example ~/Notes/personal. Create it first if it does not exist.
2. Logseq writes a logseq/ config subdirectory and a pages/ directory inside that folder. Leave those alone unless you know what you are changing.
3. Open Settings → Editor and confirm the file format (Markdown is the default and most portable choice).
4. Optionally set a preferred theme under Settings → Themes. The built-in dark mode works well on both X11 and Wayland.

You can have multiple graphs — one for work, one personal. Switch between them via Graphs in the left sidebar.

Using Daily Notes

Daily notes are Logseq's journaling backbone. Each day gets its own page, automatically titled with the date.

• Press t d (or click the calendar icon in the left sidebar) to jump to today's journal page.
• Type bullet points freely. Indent with Tab, outdent with Shift+Tab.
• Reference any other page by typing [[Page Name]] — Logseq creates the page if it does not exist and builds a bi-directional link automatically.
• Tag tasks with TODO or DOING at the start of a block. Toggle task state with Ctrl+Enter.
• Use / to open the command palette mid-block: insert timestamps, templates, embeds, and more.

Daily notes accumulate into a queryable timeline. You can find past entries from any linked page's Linked References section at the bottom of that page.

Installing Plugins

Logseq has a built-in plugin marketplace. Enable it first:

1. Go to Settings → Advanced and turn on Developer mode. This unlocks the plugin panel.
2. Click the puzzle-piece icon in the toolbar (or press t p) to open the Plugin Center.
3. Search and install. Recommended starting plugins:

• Logseq Agenda — surfaces TODO items and deadlines in a calendar view.
• Bullet Threading — adds visual thread lines to deeply nested outlines.
• Journals Calendar — mini calendar in the sidebar for navigating daily notes.
• Markdown Table Editor — turns raw Markdown tables into a spreadsheet-style editor.

Plugins run inside Logseq's Electron sandbox. Still, only install plugins from the official marketplace or well-known open-source authors — they have access to your file system within the graph directory.

Syncing Across Devices

Because your graph is plain files, any file-sync tool works. Three practical options:

Option 1: Syncthing (recommended, self-hosted, free)

Syncthing does peer-to-peer sync with no cloud middleman.

# Debian / Ubuntu
sudo apt install syncthing
systemctl --user enable --now syncthing

# Fedora
sudo dnf install syncthing
systemctl --user enable --now syncthing

# Arch
sudo pacman -S syncthing
systemctl --user enable --now syncthing

Open http://127.0.0.1:8384 in a browser to configure Syncthing. Add your ~/Notes/personal folder as a shared folder and pair with your other devices (phone, second laptop). On Android, use the official Syncthing-Fork app alongside Logseq Mobile.

Option 2: Git with a private remote

Commit your graph to a private Git repository (self-hosted Gitea, or a private GitHub/GitLab repo). Use the Git plugin inside Logseq for automatic commits, or do it manually:

cd ~/Notes/personal
git init
echo 'logseq/bak/' >> .gitignore
git add -A
git commit -m "initial graph"
git remote add origin [email protected]:youruser/notes.git
git push -u origin main

The Logseq Git plugin can auto-commit every N minutes. Configure it under Plugin Settings → Git after installing it from the Plugin Center.

Option 3: Logseq Sync (official, paid)

Logseq offers end-to-end encrypted hosted sync. As of 2024 it is available as a subscription inside the app under Settings → Logseq Sync. Useful if you want zero self-hosting overhead, but the free options above are fully functional.

Verification

After setup, confirm everything is working:

1. Open Logseq and navigate to today's journal page (t d). Write a test note with a [[Test Page]] link.
2. Click that link — Logseq opens the new page and shows the journal entry under Linked References at the bottom.
3. Press g s to open the graph view. You should see at least two nodes connected by an edge.
4. If using Syncthing, check that the pages/ directory appeared on your second device within a minute or two of saving.

Troubleshooting

• Blank white screen on launch: Usually a GPU rendering issue in Electron. Try launching with --disable-gpu appended to the Exec line in your .desktop file.
• AppImage does not open at all: Run it from the terminal to see the actual error. Missing libfuse2 is the most common cause (see installation step above).
• Plugins not loading after update: Logseq occasionally breaks plugin APIs between releases. Check the plugin's GitHub issues, or temporarily disable all plugins via Settings → Plugins to isolate the problem.
• Sync conflicts (Syncthing): Syncthing renames the conflicting file rather than silently overwriting. You will see a file like pagename.sync-conflict-....md in your pages/ folder. Open both files, merge manually, and delete the conflict copy.
• Wayland rendering artifacts: Add --ozone-platform=wayland to the Exec line. This enables native Wayland mode in the underlying Electron/Chromium runtime.