- Clojure 71.1%
- OCaml 10.3%
- JavaScript 7.9%
- CSS 3.7%
- Swift 1.5%
- Other 5.4%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
f11f5f81ee
Some checks failed
build-android.yml / enhance(rtc): support E2EE graphs in semantic API and PATs (#13671) (push) Failing after 0s
Build and Sync Plugin Docs / build-and-sync-docs (push) Has been skipped
CI / test (ubuntu-22.04) (push) Waiting to run
CI / CLI E2E tests (push) Waiting to run
CI / Spell Check with Typos (push) Waiting to run
CI / lint (push) Waiting to run
CLI sync stress / CLI sync/offline stress (push) Waiting to run
Clojure E2E / Build (push) Waiting to run
Clojure E2E / Test commands (push) Blocked by required conditions
Clojure E2E / Test editor (push) Blocked by required conditions
Clojure E2E / Test graph-properties (push) Blocked by required conditions
Clojure E2E / Test outliner-rtc (push) Blocked by required conditions
Clojure E2E / Test remaining (push) Blocked by required conditions
Clojure E2E / Mark success (push) Blocked by required conditions
Clojure RTC E2E / Build (push) Waiting to run
Clojure RTC E2E / Test run-rtc-extra-part2-test (push) Blocked by required conditions
Clojure RTC E2E / Test run-rtc-extra-test (push) Blocked by required conditions
logseq/cli CI / release (push) Has been skipped
CI / db-graph-test (ubuntu-latest) (push) Failing after 7s
logseq/cli CI / test (push) Failing after 4s
logseq/db-sync CI / test (push) Failing after 4s
logseq/db-sync CI / lint (push) Failing after 3s
logseq/outliner CI / test (push) Failing after 4s
logseq/outliner CI / lint (push) Failing after 3s
* enhance(rtc): support E2EE graphs in semantic API and PATs PATs can now be created for E2EE-encrypted graphs and the semantic API serves them end to end: - Edge helpers: GET /e2ee/public-keys, POST /e2ee/encrypt and POST /e2ee/decrypt so agents don't reimplement transit+AES-GCM. - Encrypt accepts either a caller-supplied AES key (canonical [iv ciphertext] package) or no key, producing an RSA-envelope package with an ephemeral AES key wrapped to every member's RSA public key — agents need no secrets to write. - A graph-scoped PAT may GET /e2ee/graphs/:id/aes-key for its own graph to bootstrap decryption (also exposes a base64 form of the wrapped key); all other /e2ee index routes stay 403 for PATs. - Writes to E2EE graphs must submit encrypted packages: title/body fields that are not valid ciphertext return 400. Reads return ciphertext unchanged. - Page create skips title validation and namespace splitting for encrypted titles, and [[ref]] extraction is skipped on E2EE graphs since titles are opaque. - listGraphs/graphGet expose graph-e2ee? instead of filtering E2EE graphs out. - Client-side decrypt understands RSA-envelope packages by unwrapping with the user's RSA private key. - Settings > Encryption shows the public key and reveals the private key only after password verification; the PAT graph picker lists E2EE graphs with an (E2EE) label. * fix(rtc): pass index e2ee flag to DO and harden semantic input validation The DO-side e2ee write gate relied solely on the graph DB's :logseq.kv/graph-rtc-e2ee? kv, which is only populated at RTC upload. Freshly created encrypted graphs (index flag already set) therefore accepted plaintext writes and ciphertext titles hit page-name validation. The edge now forwards the authoritative index flag as a graph-e2ee search param and the DO gates on kv-or-param. Also fixes malformed inputs returning 500 instead of 400: malformed JSON bodies (body-clj swallows parse errors so existing missing-field checks fire), non-string titles (seq throws on numbers), and non-sequential blocks/entries collections. Blocks title collection no longer misuses concat as a transducer. * enhance(rtc): serve semantic api on local node adapter Routes /openapi.json and /api/* through the same worker dispatch in the local node adapter, with a LOGSEQ_SYNC_DO stand-in that forwards to the local graph context and unlimited rate limiters, so the semantic REST API can be exercised end-to-end against a local server. * fix(rtc): clean up lint warnings in e2ee helpers * fix(rtc): decode transit private key before password reveal reveal-private-key! passed the raw transit string to e2ee-password-to-decrypt-private-key, so <decrypt-private-key's vector? assertion threw a non-decrypt-private-key error that the dialog's catch ignored — revealing the key silently failed for every password. Decode it the same way the public key already is. * enhance(rtc): describe E2EE ops in MCP tool descriptors * enhance(rtc): expose semantic API ops as individual MCP tools * fix(rtc): accept ciphertext titles in semantic API update ops Encrypted titles are opaque ciphertext packages: skip page-title and property-name validation on e2ee graphs for pages-update, tags-update, properties-create and properties-update. Without this, valid encrypted writes 500'd on title characters like '/'. * docs(rtc): add logseq-rest-api skill Covers PAT auth, op request shapes, the E2EE ciphertext-title flow (encrypt helper, AES key unwrap, decrypt), and the empirically-verified list of ops that are unusable or degraded on E2EE graphs. * docs(rtc): clarify e2ee references limitation in rest api skill * fix(rtc): preserve graph encryption in semantic API Use canonical graph AES packages, preserve separately encrypted names, and validate encrypted asset streams before creating graph records. Guard plaintext MCP file tools and add encrypted write/download coverage. * fix(rtc): reject oversized encrypted streams early Bound ciphertext chunks by the declared plaintext size before the fixed-length upload stream can overflow. Exercise encrypted uploads with a fixed-length stream and verify invalid-size cleanup. * fix(rtc): drain streamed asset bodies in the local node bucket R2's put consumes the upload ReadableStream, which pulls the encrypted-package and fixed-length transform chains to completion. The filesystem bucket wrapped the stream object itself as bytes, leaving the pipe promises unsettled and hanging uploads locally with zero-byte files. Drain web streams to bytes before writing. * fix(rtc): pass ASSET_LINK_SECRET through to the local node adapter The local adapter's env-object only forwarded a fixed set of bindings, so asset link signing (getAsset downloads) always failed with "missing ASSET_LINK_SECRET" when running the node adapter locally. * fix(rtc): complete local encrypted asset handling Stream asset bodies into atomic filesystem uploads, clean up failed streams, and validate signed downloads in the Node adapter. Document task dates as Unix millisecond timestamps and cover filesystem and HTTP behavior with regression tests. |
||
| .agents/skills | ||
| .carve | ||
| .claude | ||
| .clj-kondo | ||
| .github | ||
| .lsp | ||
| .spec-dev-tool/guides | ||
| android | ||
| assets | ||
| bin | ||
| cli | ||
| cli-e2e | ||
| clj-e2e | ||
| deps | ||
| dist | ||
| docs | ||
| externs | ||
| fastlane/metadata/android/en-US | ||
| icons | ||
| ios | ||
| libs | ||
| prompts | ||
| public | ||
| resources | ||
| scripts | ||
| sidecar | ||
| src | ||
| .cljfmt.edn | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .i18n-lint.toml | ||
| .npmrc | ||
| .prettierrc.js | ||
| .projectile | ||
| .stylelintrc.json | ||
| AGENTS.md | ||
| bb.edn | ||
| capacitor.config.ts | ||
| CODE_OF_CONDUCT.md | ||
| CODEBASE_OVERVIEW.md | ||
| CONTRIBUTING.md | ||
| deps.edn | ||
| Dockerfile | ||
| externs.js | ||
| gulpfile.js | ||
| LICENSE.md | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| postcss.config.js | ||
| README.md | ||
| shadow-cljs.edn | ||
| tailwind.all.css | ||
| tailwind.config.js | ||
| tailwind.mobile.css | ||
| typos.toml | ||
| webpack.config.js | ||
Logseq
A privacy-first, open-source platform for knowledge management and collaboration
Table of Contents
- 🚀 Database Version
- 🤔 Why Logseq?
- 👀 How can I use it?
- 📚 Learn more
- 🫶 Support Logseq Development
- 💡 Feature requests
- 🔌 Plugin API
- 🌟 Contributing to Logseq
- ✨ Inspiration
- 🙏 Thank You
🚀 Database Version
The Database version (DB version) of Logseq introduces DB graphs. See this page to get an overview of the main features for DB graphs. If you are an existing user, see changes with the DB version. The DB version has its own new mobile app (on iOS, with Android coming soon)! To participate in the mobile app alpha, please complete this brief form. The DB version also has a new sync approach, RTC (Real Time Collaboration)! You can use it to sync graphs between multiple devices or collaborate with others. To participate in the RTC alpha, please fill out this form.
The DB version is in beta status while the new mobile app and RTC is in alpha. This means that data loss is possible so we recommend automated backups or regular SQLite DB backups. We recommend you create a dedicated test graph and choose one project that’s not crucial for you.
To get started with the DB version:
- To try the latest web version, go to https://app.logseq.com/.
- To try the latest desktop version, go to https://github.com/logseq/logseq/releases/tag/nightly and download the artifact for your operating system.
- To try the latest by building from the source code
- Use
test/dbfor stable releases. Fewer bugs and slower updates. Update frequency: days or weeks. - Use
masterfor the latest updates as they are developed. Expect more bugs and faster changes. Update frequency: hours or days.
- Use
- To report bugs, please file them at https://github.com/logseq/db-test/issues.
- For feature or enhancement requests, please file them on Discord on the
#db-feedbackchannel. - For discussions:
- General ==> see the
#db-chatchannel in Discord. - Sync and RTC ==> see the
#sync-testchannel in Discord. - Mobile ==> see the
#mobile-testchannel in Discord.
- General ==> see the
🤔 Why Logseq?
Logseq is a knowledge management and collaboration platform. It focuses on privacy, longevity, and user control. Logseq offers a range of powerful tools for knowledge management, collaboration, PDF annotation, and task management with support for multiple file formats, including Markdown and Org-mode, and various features for organizing and structuring your notes.
In addition to its core features, Logseq has a growing ecosystem of plugins and themes that enable a wide range of workflows and customization options. Mobile apps are also available, providing access to most of the features of the desktop application. Whether you're a student, a professional, or anyone who values a clear and organized approach to managing your ideas and notes, Logseq is an excellent choice for anyone looking to improve their productivity and streamline their workflow.
👀 How can I use it?
To start using Logseq, follow these simple steps:
- Download the latest version of Logseq
- Install Logseq on your device and launch the application
- Start writing ✍️
That's it! You can now enjoy the benefits of using Logseq to streamline your workflow, manage your projects, and stay on top of your goals. Have fun! 🎉
Linux users: Use the automated installer script for the best experience:
# Download and run the installer
curl -fsSL https://raw.githubusercontent.com/logseq/logseq/master/scripts/install-linux.sh | bash
# Or install a specific version
curl -fsSL https://raw.githubusercontent.com/logseq/logseq/master/scripts/install-linux.sh | bash -s -- 0.10.14
# For user-specific installation (no root required)
curl -fsSL https://raw.githubusercontent.com/logseq/logseq/master/scripts/install-linux.sh | bash -s -- --user
📚 Learn more
- Website: logseq.com
- Documentation: docs.logseq.com
- FAQ page: Logseq Docs: FAQ
- Blog: blog.logseq.com
- Please visit our About page for the latest updates.
- Forum: discuss.logseq.com - Where we answer questions, discuss workflows, and share tips
- FAQ forum section: Logseq Forum: FAQ
- Awesome Logseq - Awesome Logseq extensions and resources created by the community <3
- Twitter: @Logseq
- Discord: https://discord.com/invite/KpN4eHY
🫶 Support Logseq Development
If you find Logseq useful and want to help us keep the project growing, please consider supporting our contributors on Open Collective. Your support shows our contributors that their efforts are appreciated and motivates them to continue their excellent work. Every contribution, no matter how small, helps us keep improving Logseq.
💡 Feature requests
We value your input on improving Logseq and making it more useful for you. If you have any ideas or feature requests, please share them in the Logseq Forum: Feature Requests section.
Your feedback helps us understand our users' needs and prioritize the features that matter most to you. We appreciate your time and effort in sharing your thoughts with us.
We appreciate your support, and we look forward to hearing your ideas!
🔌 Plugin API
Logseq provides a plugin API that enables developers to create custom plugins and extend the functionality of Logseq. The plugin API documentation is available at plugins-doc.logseq.com, where you can find everything needed to get started with plugin development.
We value your feedback and suggestions on how to improve our documentation. Please do not hesitate to contact us with any comments or questions. Your input helps us to provide a better experience for our users and developers.
Thank you for using Logseq, and we look forward to seeing what you create with our plugin API!
🌟 Contributing to Logseq
To start contributing to Logseq, please read CONTRIBUTING.md. There are ways to contribute with code and without code. We welcome all contributions, big or small, and we appreciate your time and effort in helping us improve Logseq. We look forward to your contributions 🚀
🛠️ Setting Up a Development Environment
If you want to set up a development environment for the Logseq web or desktop app, please refer to the Develop Logseq guide for macOS/Linux users and the Develop Logseq on Windows guide for Windows users.
In addition to these guides, you can also find other helpful resources in the docs/ folder, such as the Guide for Contributing to Translations, the Docker Web App Guide and the mobile development guide
🧰 Logseq CLI (Node)
Logseq CLI documentation is maintained in docs/cli/logseq-cli.md.
✨ Inspiration
Logseq is inspired by several unique tools and projects, including Roam Research, Org Mode, TiddlyWiki, Workflowy, and Cuekeeper.
We owe a huge debt of gratitude to the developers and creators of these projects, and we hope that Logseq can continue to build on their innovative ideas and make them accessible to a broader audience.
Thank you to all those who inspire us, and we look forward to seeing what the Logseq community will create with this tool!
Logseq is also made possible by the following projects:
- Clojure & ClojureScript - A dynamic, functional, general-purpose programming language
- DataScript - An immutable database and Datalog query-engine for Clojure, ClojureScript and JS
- OCaml & Angstrom, for the document parser mldoc
- isomorphic-git - A pure JavaScript implementation of Git for NodeJS and web browsers
- SCI - A Small Clojure Interpreter
🙏 Thank You
We want to express our sincere gratitude to our Open Collective sponsors, backers, and contributors. Your support and contributions allow us to continue developing and improving Logseq. Thank you for being a part of our community and helping us make Logseq the best it can be!
💎 Sponsors
🌟 Contributors
