Skip to content

qurtai/qurt

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

78 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Qurt logo

AI Coworker and assistant with provider freedom: bring your own API keys, choose your model, and chat with files/images in one place.

Release Build Desktop Downloads Stars Electron TypeScript

Showcase

Why Qurt

  • Provider freedom first: connect your own provider keys and avoid lock-in.
  • Desktop-native workflow: keep your chats, files, and context in one local app.
  • Built for practical AI work: switch models, attach files/images, and iterate quickly.

Features

  • Bring-your-own-key model access
  • Multi-provider model selection
  • Chat with file and image attachments
  • Local-first data approach for keys and chat context
  • Modern Electron + React + TypeScript stack

Install

Option 1: Download from GitHub Releases

  1. Open the latest release.
  2. Download the installer for your platform.
  3. Install and launch Qurt.

Option 2: Run from source

npm install
npm run dev

Development

# install dependencies
npm install

# run desktop app in development mode
npm run dev

# build app
npm run build

# package distributables
npm run dist

# lint
npm run lint

# tests
npm run test

Release And Auto-Update Strategy

Release pipeline

Pushing a version tag (e.g. v0.1.0) triggers the release workflow:

  1. Runs tests
  2. Builds Windows (Squirrel) and macOS (DMG, ZIP) installers
  3. Creates a GitHub Release with auto-generated notes and uploads all artifacts

To release:

# 1. Bump version in package.json (e.g. 0.1.0 → 0.1.1)
npm version patch   # or minor / major

# 2. Push the version commit and tag
git push && git push --tags

Tags like v0.1.0-beta.1 are marked as prereleases. The workflow runs on every push to tags matching v*.

Maintainer checklist

  1. Build and publish desktop artifacts on release tags (automated via .github/workflows/build-desktop.yml).
  2. Publish installers/artifacts to GitHub Releases (automated).
  3. Keep update-electron-app configured in the main process so packaged clients can pull updates from the GitHub release feed.

Documentation

  • Product and architecture docs live in docs/.

Contributing

Issues and pull requests are welcome. If you want to help shape the open-source direction, open an issue describing the use case or improvement idea first.

License

MIT — see LICENSE.

Sponsor this project

Contributors

Languages