diff --git a/.env.example b/.env.example
index 9b23136..ad9d65d 100644
--- a/.env.example
+++ b/.env.example
@@ -24,3 +24,11 @@ GITHUB_TOKEN=
# Production and the deploy workflow use `/` (the site is served from the apex
# domain). Override only when previewing under a sub-path, e.g. `/my-fork/`.
ASTRO_BASE=/
+
+# Public analytics identifiers injected at build time. These values are visible
+# in the generated HTML/browser and are identifiers, not secrets.
+PUBLIC_CLOUDFLARE_WEB_ANALYTICS_TOKEN=
+PUBLIC_GOOGLE_ANALYTICS_ID=
+
+# Optional Google Search Console HTML-tag verification value.
+PUBLIC_GOOGLE_SITE_VERIFICATION=
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 85ffb02..841b490 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -4,7 +4,14 @@
## Validation
+- [ ] `npm test`
- [ ] `npm run build`
+- [ ] Cloudflare branch preview checked on desktop and mobile
+
+## Content checks
+
+- [ ] Claims, organizations, sponsors, and metrics have a verifiable source
+- [ ] New internal links work with `ASTRO_BASE`
## Notes
diff --git a/.github/workflows/deploy-pages.yml b/.github/workflows/deploy-pages.yml
deleted file mode 100644
index 6fbd802..0000000
--- a/.github/workflows/deploy-pages.yml
+++ /dev/null
@@ -1,59 +0,0 @@
-name: Deploy to GitHub Pages
-
-on:
- push:
- branches:
- - main
- workflow_dispatch:
-
-permissions:
- contents: read
- pages: write
- id-token: write
-
-env:
- FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
-
-concurrency:
- group: pages
- cancel-in-progress: false
-
-jobs:
- build:
- runs-on: ubuntu-latest
- steps:
- - name: Checkout
- uses: actions/checkout@v7
-
- - name: Setup Node
- uses: actions/setup-node@v7
- with:
- node-version: 22
- cache: npm
-
- - name: Setup Pages
- uses: actions/configure-pages@v6
-
- - name: Install dependencies
- run: npm ci
-
- - name: Build site
- env:
- ASTRO_BASE: /
- run: npm run build
-
- - name: Upload artifact
- uses: actions/upload-pages-artifact@v5
- with:
- path: dist
-
- deploy:
- needs: build
- runs-on: ubuntu-latest
- environment:
- name: github-pages
- url: ${{ steps.deployment.outputs.page_url }}
- steps:
- - name: Deploy to GitHub Pages
- id: deployment
- uses: actions/deploy-pages@v5
diff --git a/.github/workflows/sync-content.yml b/.github/workflows/sync-content.yml
index 6e5164b..9183bb3 100644
--- a/.github/workflows/sync-content.yml
+++ b/.github/workflows/sync-content.yml
@@ -23,8 +23,6 @@ on:
permissions:
contents: write
- pages: write
- id-token: write
env:
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
@@ -48,10 +46,6 @@ jobs:
node-version: 22
cache: npm
- - name: Setup Pages
- if: ${{ github.ref == 'refs/heads/main' }}
- uses: actions/configure-pages@v6
-
- name: Install dependencies
run: npm ci
@@ -112,14 +106,3 @@ jobs:
- name: Push synced data
if: ${{ steps.commit.outputs.changed == 'true' }}
run: git push
-
- - name: Upload Pages artifact
- if: ${{ steps.commit.outputs.changed == 'true' && github.ref == 'refs/heads/main' }}
- uses: actions/upload-pages-artifact@v5
- with:
- path: dist
-
- - name: Deploy synced data to GitHub Pages
- if: ${{ steps.commit.outputs.changed == 'true' && github.ref == 'refs/heads/main' }}
- id: deployment
- uses: actions/deploy-pages@v5
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9f701b9..125625e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -6,13 +6,13 @@ Thanks for helping improve IndopenSource.org.
```bash
npm install
-npm run sync:projects
npm run dev
```
Before opening a pull request:
```bash
+npm test
npm run build
```
@@ -35,13 +35,41 @@ Use `GITHUB_TOKEN` or `GH_TOKEN` to avoid low GitHub API rate limits.
`main` commit to production.
- Keep changes focused.
- Prefer Astro components in `src/components` over large page-only markup.
-- Keep internal links compatible with GitHub Pages base paths by using `withBase()`.
-- Run `npm run build` and include the result in the PR description.
+- Use `withBase()` for internal links that must remain valid when `ASTRO_BASE`
+ is set by CI or a preview environment.
+- Run `npm test` and `npm run build`, then include the results in the PR description.
- For content or roadmap changes, link the relevant issue or discussion.
+## Community Directory
+
+The Community page reads `src/data/communities.json`. To propose one community,
+add one object containing:
+
+- `name`
+- `description`
+- `url` pointing to an official channel
+- optional `focus`
+- optional `location`
+
+Keep one community per pull request and explain your relationship to it or add a
+source that reviewers can verify. Do not add inferred or inactive communities.
+
+## Content Quality
+
+- Lead with a direct summary before background detail.
+- Cite primary sources for factual claims and include the relevant date.
+- Use descriptive headings and stable internal links to related pages.
+- Identify authors and keep publication and update dates traceable.
+- Do not add speculative facts, generated statistics, or special AI-search
+ markup that is not supported by search-engine documentation.
+
## Production Release
The `release` branch is reserved for Cloudflare production deployments. Only
IndopenSource organization members may update it, through a pull request from
`main` that passes CI. Merge production promotion pull requests with a merge
commit so `main` remains in the `release` history.
+
+Cloudflare creates a branch preview for contribution pull requests. Review that
+preview before promoting `main` to `release`; use
+[`docs/release-checklist.md`](docs/release-checklist.md) for the production pass.
diff --git a/README.md b/README.md
index ddba074..07453ef 100644
--- a/README.md
+++ b/README.md
@@ -1,35 +1,42 @@
+
+
# IndopenSource.org
-[](https://github.com/IndopenSource/indopensource.org/actions/workflows/deploy-pages.yml)
+[](https://github.com/IndopenSource/indopensource.org/actions/workflows/ci.yml)
[](LICENSE)
-Website roadmap untuk `https://indopensource.org`.
+Website komunitas dan direktori open source Indonesia di `https://indopensource.org`.
## Tech Stack
- Astro
- Tailwind CSS
- TypeScript
-- GitHub Pages
- GitHub Actions
+- Cloudflare Workers Static Assets
## Pages
-- Home: ringkasan roadmap dan arah website.
+- Home: pintu masuk ke direktori, roadmap, pembelajaran, dan kontribusi.
- Falsafah: prinsip komunitas dan kurasi open source Indonesia.
-- Projects: direktori dari `IndopenSource/awesome-indonesia`.
-- Blog: placeholder untuk repo khusus `IndopenSource/Blog-IndopenSource`.
-- Forum: rencana integrasi `https://github.com/orgs/IndopenSource/discussions`.
-- Contact: kanal GitHub organization, projects, dan discussions.
+- Projects: direktori proyek dari `IndopenSource/awesome-indonesia`.
+- Top User: peringkat pemilik repository berdasarkan akumulasi stars.
+- Komunitas: direktori komunitas yang diusulkan melalui pull request.
+- Roadmap: rencana kerja publik 2026–2027.
+- Belajar dan Blog: materi serta artikel yang disinkronkan dari repository sumber.
+- Donasi: informasi OpenSawer, sponsorship, CSR, dan dukungan non-dana.
+- Forum dan Kontak: GitHub Discussions serta kanal resmi IndopenSource.
## Development
```bash
npm install
-npm run sync:projects
npm run dev
```
+Sinkronisasi data bersifat opsional untuk pengembangan UI. File hasil sinkronisasi
+yang diperlukan sudah tersedia di `src/data/`.
+
## Project Structure
```txt
@@ -45,38 +52,34 @@ src/
## Checks
```bash
+npm test
npm run check
npm run build
```
-## MVP Pre-release
-
-MVP awal berfokus pada homepage sebagai pintu masuk roadmap IndopenSource:
-
-- Home menjelaskan posisi `indopensource.org`.
-- Projects sudah punya data awal dari `awesome-indonesia`.
-- Falsafah, Blog, Forum, dan Contact tersedia sebagai halaman roadmap.
-- Deployment memakai GitHub Pages bawaan repo lewat GitHub Actions.
-
-Rilis pre-release bisa dibuat dari tag `v0.1.0-mvp` setelah workflow Pages hijau.
-URL produksi setelah custom domain aktif adalah `https://indopensource.org/`.
-
## Deployment
-Deployment saat ini masih memakai GitHub Pages melalui workflow
-`.github/workflows/deploy-pages.yml`. Cloudflare production berikutnya akan
-dibangun dari branch `release`.
+Cloudflare terhubung langsung ke repository dan membuat preview untuk pull
+request atau branch non-production. Production hanya dibangun dari branch
+`release`.
- Build command: `npm run build`
+- Deploy command: `npx wrangler deploy`
- Output directory: `dist`
-- Source: GitHub Actions
+- Konfigurasi Worker: `wrangler.jsonc`
+- Production branch: `release`
- Custom domain: `indopensource.org`
-- Pages base path: `/`
-Semua kontribusi tetap masuk ke `main`. Rilis produksi dipromosikan oleh anggota
-organisasi melalui pull request dari `main` ke `release`; jangan membuka pull
+Semua kontribusi masuk ke `main`. Anggota organisasi mempromosikan versi yang
+sudah diuji melalui pull request dari `main` ke `release`; jangan membuka pull
request kontribusi langsung ke `release`.
+GitHub Pages sudah tidak digunakan. Deployment dan preview website ditangani
+oleh Cloudflare; workflow sinkronisasi konten hanya memperbarui data di `main`.
+
+Lihat [checklist release](docs/release-checklist.md) sebelum mempromosikan
+`main` ke `release`.
+
## Project Sync
`npm run sync:projects` membaca `repos.json` dari `IndopenSource/awesome-indonesia`,
@@ -88,8 +91,14 @@ Gunakan `GITHUB_TOKEN` atau `GH_TOKEN` untuk rate limit yang lebih lega.
## Blog Sync
`npm run sync:blog` membaca artikel Markdown dari
-`IndopenSource/Blog-IndopenSource`, mengambil metadata commit penulis/rilis,
-dan menulis hasilnya ke `src/data/blog-posts.json`.
+`IndopenSource/Blog-IndopenSource`, mengambil tanggal commit pertama, commit
+terbaru, dan seluruh kontributor unik setiap artikel, lalu menulis hasilnya ke
+`src/data/blog-posts.json`. Halaman artikel menautkan commit terbaru tersebut
+agar riwayat sumber dapat diperiksa langsung.
+
+Artikel berstatus `draft` tetap dibangun pada URL `/blog/preview/{slug}/`,
+tetapi tidak ditampilkan di indeks blog, tidak masuk sitemap, dan memakai
+`noindex, nofollow, noarchive` sampai statusnya diterbitkan.
## Auto Sync
@@ -103,8 +112,20 @@ Workflow `.github/workflows/sync-content.yml` memperbarui data secara otomatis.
- `sync-content`
Jika data berubah, workflow membuat commit `Sync content data`. Setelah commit
-masuk `main`, workflow yang sama akan upload artifact dan deploy ulang GitHub
-Pages agar perubahan data langsung tayang.
+masuk `main`, perubahan mengikuti validasi dan alur promosi `main` ke `release`.
+Cloudflare kemudian membuat preview `main`; production tetap dipromosikan lewat
+pull request ke `release`.
+
+## Analytics & Search Verification
+
+Analytics aktif saat build Cloudflare menerima environment variable berikut:
+
+- `PUBLIC_CLOUDFLARE_WEB_ANALYTICS_TOKEN`
+- `PUBLIC_GOOGLE_ANALYTICS_ID` (format `G-XXXXXXXXXX`)
+- `PUBLIC_GOOGLE_SITE_VERIFICATION` (opsional)
+
+Nilainya merupakan identifier publik dan tidak perlu dimasukkan ke Git. Isi di
+pengaturan build Cloudflare untuk production dan preview sesuai kebutuhan.
## Contributing
diff --git a/docs/assets/indopensource-banner.png b/docs/assets/indopensource-banner.png
new file mode 100644
index 0000000..9ff739a
Binary files /dev/null and b/docs/assets/indopensource-banner.png differ
diff --git a/docs/release-checklist.md b/docs/release-checklist.md
new file mode 100644
index 0000000..557a3d9
--- /dev/null
+++ b/docs/release-checklist.md
@@ -0,0 +1,33 @@
+# Release checklist
+
+Production is promoted from `main` to `release` through a pull request opened by
+an IndopenSource organization member.
+
+## Before promotion
+
+- [ ] Contribution pull requests are merged into `main` and CI is green.
+- [ ] Cloudflare branch preview has been checked on desktop and mobile.
+- [ ] `npm test` and `npm run build` pass from the intended release commit.
+- [ ] Navigation, project detail pages, `/donasi/`, `/komunitas/`, `/roadmap/`,
+ `/sitemap.xml`, and the `/sponsors/` redirect have been checked.
+- [ ] `admin@`, `press@`, `sponsor@`, and `legal@indopensource.org` can receive
+ mail, or links to inactive addresses have been removed.
+- [ ] DNS, custom domain, TLS, and the Cloudflare production branch are correct.
+- [ ] Cloudflare build variables for the Web Analytics token and Google
+ Analytics Measurement ID are configured.
+
+## Promote
+
+1. Open a pull request from `main` to `release`.
+2. Require green CI and review the diff for unexpected generated data.
+3. Merge with a merge commit so `main` remains in the `release` history.
+4. Wait for the Cloudflare production deployment to pass.
+
+## After deployment
+
+- [ ] Smoke-test `https://indopensource.org/` and the primary navigation.
+- [ ] Confirm canonical URLs, robots, sitemap, favicon, and social previews.
+- [ ] Confirm Cloudflare Web Analytics and Google Analytics receive a test page
+ view without CSP errors.
+- [ ] Send a test message to each published email address.
+- [ ] Record the production commit or tag as the rollback point.
diff --git a/public/_redirects b/public/_redirects
new file mode 100644
index 0000000..54b9661
--- /dev/null
+++ b/public/_redirects
@@ -0,0 +1 @@
+/sponsors/ /donasi/ 301
diff --git a/public/brand/apple-touch-icon.png b/public/brand/apple-touch-icon.png
index e36db39..b50d69a 100644
Binary files a/public/brand/apple-touch-icon.png and b/public/brand/apple-touch-icon.png differ
diff --git a/public/brand/favicon-96.png b/public/brand/favicon-96.png
new file mode 100644
index 0000000..4c9183a
Binary files /dev/null and b/public/brand/favicon-96.png differ
diff --git a/public/brand/favicon.ico b/public/brand/favicon.ico
index 815d094..29eb739 100644
Binary files a/public/brand/favicon.ico and b/public/brand/favicon.ico differ
diff --git a/public/brand/tokengratis-icon.png b/public/brand/tokengratis-icon.png
new file mode 100644
index 0000000..bfebf7c
Binary files /dev/null and b/public/brand/tokengratis-icon.png differ
diff --git a/scripts/sync-blog-posts.mjs b/scripts/sync-blog-posts.mjs
index 661eaac..a6153a9 100644
--- a/scripts/sync-blog-posts.mjs
+++ b/scripts/sync-blog-posts.mjs
@@ -161,6 +161,20 @@ async function getCommitMeta(path) {
const firstCommit = commits.at(-1);
const latestCommit = commits.at(0);
const author = firstCommit?.author;
+ const authors = [];
+ const seenAuthors = new Set();
+
+ for (const item of commits.toReversed()) {
+ const name = item.author?.login || item.commit?.author?.name;
+ if (!name || seenAuthors.has(name.toLowerCase())) continue;
+ seenAuthors.add(name.toLowerCase());
+ authors.push({
+ name,
+ avatarUrl: item.author?.avatar_url || '',
+ url: item.author?.html_url || '',
+ committedAt: item.commit?.author?.date || ''
+ });
+ }
return {
author: {
@@ -169,6 +183,9 @@ async function getCommitMeta(path) {
url: author?.html_url || firstCommit?.html_url || `https://github.com/${BLOG_REPO}`,
committedAt: firstCommit?.commit?.author?.date || ''
},
+ authors,
+ latestCommitSha: latestCommit?.sha || '',
+ latestCommitUrl: latestCommit?.html_url || '',
// The latest commit timestamp is the date of the most recent EDIT, not a
// publication/release event (CC-9). Name it honestly as "last modified" so
// the rendered label can stop calling an edit timestamp a release date.
@@ -244,6 +261,14 @@ for (const path of articleFiles) {
const commitMeta = await getCommitMeta(path);
const editorialDate = (data.date || '').trim();
const resolvedAuthor = resolveAuthor(commitMeta.author, data.authors);
+ const resolvedAuthors = resolvedAuthor.fromFrontmatter
+ ? [
+ resolvedAuthor.author,
+ ...commitMeta.authors.filter(
+ (author) => author.name.toLowerCase() !== (resolvedAuthor.author?.name || '').toLowerCase()
+ )
+ ]
+ : commitMeta.authors.length ? commitMeta.authors : [resolvedAuthor.author];
posts.push({
slug: slugFromPath(path),
@@ -264,7 +289,10 @@ for (const path of articleFiles) {
// edit timestamp separately for provenance (CC-9).
releasedAt: editorialDate || commitMeta.author.committedAt || commitMeta.lastModifiedAt,
lastModifiedAt: commitMeta.lastModifiedAt,
+ latestCommitSha: commitMeta.latestCommitSha,
+ latestCommitUrl: commitMeta.latestCommitUrl,
author: resolvedAuthor.author,
+ authors: resolvedAuthors,
authorFromFrontmatter: resolvedAuthor.fromFrontmatter
});
}
diff --git a/src/components/DonationPage.astro b/src/components/DonationPage.astro
new file mode 100644
index 0000000..752b9db
--- /dev/null
+++ b/src/components/DonationPage.astro
@@ -0,0 +1,254 @@
+---
+import BaseLayout from '../layouts/BaseLayout.astro';
+import BaseButton from './BaseButton.astro';
+import PageHeader from './PageHeader.astro';
+import { withBase } from '../lib/urls';
+
+const tiers = [
+ {
+ name: 'Utama',
+ min: 'Rp 5.000.000/tahun',
+ benefits: [
+ 'Logo di homepage & footer website',
+ 'Profil organisasi di halaman sponsor',
+ 'Kolaborasi satu program atau event',
+ 'Laporan penggunaan dan dampak berkala'
+ ],
+ highlight: true
+ },
+ {
+ name: 'Partner',
+ min: 'Rp 2.500.000/tahun',
+ benefits: [
+ 'Logo di halaman sponsor & footer',
+ 'Apresiasi di kanal komunitas',
+ 'Laporan penggunaan dana berkala'
+ ],
+ highlight: false
+ },
+ {
+ name: 'Pendukung',
+ min: 'Rp 1.000.000/tahun',
+ benefits: [
+ 'Logo di halaman sponsor',
+ 'Apresiasi publik',
+ 'Akses laporan terbuka'
+ ],
+ highlight: false
+ },
+ {
+ name: 'Sahabat',
+ min: 'Rp 250.000/tahun',
+ benefits: [
+ 'Nama di halaman sponsor',
+ 'Apresiasi publik',
+ 'Akses laporan terbuka'
+ ],
+ highlight: false
+ }
+];
+
+const currentSponsors = [
+ { name: 'Tokengratis.id', since: '2026', url: 'https://tokengratis.id/', logo: withBase('/brand/tokengratis-icon.png') }
+];
+
+const openSawerIcon = "data:image/svg+xml,%3csvg%20xmlns='http://www.w3.org/2000/svg'%20width='64'%20height='64'%20viewBox='0%200%2040%2040'%3e%3ctitle%3eOpenSawer%3c/title%3e%3ccircle%20cx='20'%20cy='20'%20r='20'%20fill='%230f694e'/%3e%3ccircle%20cx='20'%20cy='11.5'%20r='3.2'%20fill='%23e8b83f'/%3e%3cpath%20d='M10.5%2019.5c1.4%207.2%205%2010.8%209.5%2010.8s8.1-3.6%209.5-10.8M12%2019.5h16'%20fill='none'%20stroke='%23fff'%20stroke-width='3.2'%20stroke-linecap='round'/%3e%3c/svg%3e";
+---
+
+
+
+
IndopenSource dijalankan oleh komunitas sukarela. Dukungan individu, sponsorship, CSR, dan kolaborasi membantu kami merawat infrastruktur, mengadakan event, dan mendukung proyek-proyek potensial.
+
+
+
+
+
+ Donasi per proyek
+
Dukung proyek yang Anda gunakan.
+
OpenSawer akan dihubungkan ke halaman setiap proyek yang terdaftar di direktori IndopenSource. Setelah integrasinya siap, siapa pun dapat memilih proyek lalu berdonasi langsung melalui kanal OpenSawer proyek tersebut.
+
Fitur ini masih dalam pengembangan dan belum tersedia di seluruh halaman proyek.
Setiap kontribusi membantu menjaga open source Indonesia tetap hidup dan berkembang.
+
+
+
+
+
+
+
+ Program CSR
+
Kami menerima dukungan CSR.
+
+ Dana CSR dapat diarahkan untuk infrastruktur komunitas, dokumentasi dan materi belajar,
+ event, serta dukungan bagi proyek open source Indonesia yang membutuhkan ruang tumbuh.
+ Program dan indikator hasil disepakati bersama perusahaan sebelum pelaksanaan.
+
+
+ Diskusikan program CSR
+
+
+
+
+
Dasar hukum dan cakupannya
+
+
+ Pasal 74 UU No. 40 Tahun 2007
+ mewajibkan Perseroan yang menjalankan usaha di bidang dan/atau berkaitan dengan sumber daya alam melaksanakan Tanggung Jawab Sosial dan Lingkungan. Anggarannya diperhitungkan sebagai biaya Perseroan dengan memperhatikan kepatutan dan kewajaran.
+
+
+ PP No. 47 Tahun 2012
+ mengatur pelaksanaannya melalui rencana kerja tahunan dan pemuatan hasil pelaksanaan dalam laporan tahunan Perseroan.
+
+
+ Pasal 15 huruf b UU No. 25 Tahun 2007
+ juga mewajibkan setiap penanam modal melaksanakan tanggung jawab sosial perusahaan. Penerapan kewajiban tetap mengikuti status, bidang usaha, dan aturan sektoral perusahaan masing-masing.
+
+
+
Informasi umum · perusahaan tetap perlu menilai kewajibannya bersama penasihat hukum.
+
+
+
+
+
+
+
+
+
+ Transparansi terbuka
+
Dana masuk, penggunaan, dan dampaknya dapat dilihat.
+
+ Penerimaan dan penggunaan dana CSR direncanakan dipublikasikan melalui OpenSawer. Laporan program,
+ rincian penyaluran, bukti kegiatan, dan pembaruan dampak akan dibuka setelah kanal pelaporan siap.
+
- Rumah terbuka untuk merawat daftar proyek, mendokumentasikan falsafah,
- menulis pembelajaran, dan menghubungkan kontributor open source Indonesia.
+ Rumah terbuka untuk merawat daftar proyek, menulis pembelajaran,
+ dan menghubungkan kontributor open source Indonesia.
\n Noise-canceling context and long-term memory for your AI agent. Stop paying Claude to read 10,000 lines of terminal noise like a headphone for AI agent\n
\n\nUp to 85% less tokens · Cross-Session Memory · ~40% faster · Zero hallucination triggers
\n
\n
Every AI coding assistant has two massive problems.
\n
1. They read everything. Build logs. Docker logs. CI logs. Progress bars. ANSI colors. Thousands of tokens... to find one line. Claude isn't expensive. Your terminal is.
\n
2. They forget everything. Every time you restart Cursor, or switch from Claude Code to Windsurf, your agent gets amnesia. You have to re-explain the project goal. You have to remind them of the same framework gotchas over and over again.
\n
OMNI fixes both.
\n\n
The Difference
\n
Problem 1: Your terminal drowns out the signal
\n
npm install
\n
Without OMNI: 10,000 lines of \"Downloading...\", \"Extracting...\", and warnings. AI reads everything. With OMNI: Package conflict. Node 20 required.
\n
terraform apply
\n
Without OMNI: 4,500 lines of unchanged execution plans. With OMNI: The 3 resources that failed IAM permissions.
\n
docker build
\n
Without OMNI: Endless cache hits, layer hashes, and download progress bars. With OMNI: Missing dependency libpq-dev at layer 12.
\n
pytest
\n
Without OMNI: 500 passing tests and verbose setup logs. With OMNI: Only the 2 failed assertions and their stack traces.
\n
cargo build
\n
Without OMNI: 300 lines of compiling dependencies and warnings. With OMNI: The exact line where the borrow checker failed.
\n
kubectl logs
\n
Without OMNI: Thousands of successful health checks and normal traffic logs. With OMNI: The crash loop and panic stack trace.
\n
git diff
\n
Without OMNI: Formatting tweaks, generated lockfiles, and whitespace changes. With OMNI: Only the core business logic changes.
\n
go test
\n
Without OMNI: Pages of standard output from passing packages. With OMNI: The single nil pointer dereference.
\n
mvn package
\n
Without OMNI: Megabytes of \"Downloading from maven central\". With OMNI: Compilation error in UserService.java.
\n
pip install
\n
Without OMNI: Resolution logs and wheel building outputs. With OMNI: Dependency conflict with numpy.
\n
webpack / vite
\n
Without OMNI: 2,000 chunk asset lists and build times. With OMNI: Missing module resolution in App.tsx.
\n
helm install
\n
Without OMNI: Entire rendered YAML output of all templates. With OMNI: Pod scheduling failure due to missing secret.
\n
ansible-playbook
\n
Without OMNI: \"ok\" and \"skipped\" statuses for 50 servers. With OMNI: The single \"failed\" task on web-03.
\n
GitHub Actions (CI/CD)
\n
Without OMNI: Complete workflow logs including environment setup. With OMNI: Only the specific step that exited with code 1.
\n
Problem 2: Your agent forgets everything overnight
\n
Starting a new session
\n
Without OMNI: \"Please re-explain the project structure, the auth module is broken, and we use Postgres not MySQL.\" With OMNI: The agent already knows. It picks up where you left off.
\n
Fixing the same bug twice
\n
Without OMNI: Agent hits the same framework gotcha it already solved yesterday because it has no memory. With OMNI: The fix is already stored. omni recall surfaces the exact solution in under 10ms.
\n
Multi-IDE workflows (Cursor → Claude Code)
\n
Without OMNI: New IDE, new agent, zero context. You're starting from scratch. With OMNI: Session summary is injected automatically. New agent is immediately up to speed.
\n\n
Why This Matters
\n
The code you don't send to the AI is just as important as the code you do.
\n
When you feed an AI megabytes of terminal noise, it suffers from context bloat—hallucinating fixes for the wrong warnings and burning your API budget on irrelevant output.
\n
When you restart an agent and it has no memory, you lose hours re-establishing context that should have been preserved automatically.
\n
OMNI solves both, invisibly:
\n
\n
Less noise → lower cost, faster responses, zero hallucination triggers.
\n
Persistent memory → no more re-explaining your project, no more repeating fixes.
\n
One install → works silently with every agent you already use.
\n
\n\n
Benchmarks
\n
The honest headline, measured on the release binary against 1,810 real command\nexecutions replayed from one developer's actual usage:
\n
\n
58.9% fewer bytes reaching the model across the whole mix (15.0 MB → 6.2 MB).
\n
63.6% of those calls saved nothing at all. OMNI handed the output straight\nback, adding zero bytes. Every byte of the saving comes from the other 36.4%,\nwhere there was real noise to cut.
\n
Structured output is never touched. JSON, YAML, NDJSON and CSV pass through\nbyte-for-byte, because a corrupted payload costs more than a missed compression.
\n
\n
That second bullet is the number most tools in this category do not print. A tool\nthat claims to save 90% of every command is telling you it summarises output you\nneeded.
\n
\n\n
Where the saving actually comes from, over the same 1,810 executions:
\n
\n\n
\n
Command
\n
Calls
\n
Input
\n
Output
\n
Saved
\n
\n\n
\n
cargo
\n
29
\n
424 KB
\n
13 KB
\n
96.8%
\n
\n
\n
git
\n
256
\n
5.9 MB
\n
509 KB
\n
91.3%
\n
\n
\n
ls
\n
52
\n
71 KB
\n
29 KB
\n
59.5%
\n
\n
\n
kubectl
\n
212
\n
4.4 MB
\n
2.3 MB
\n
48.0%
\n
\n
\n
find
\n
39
\n
83 KB
\n
53 KB
\n
36.2%
\n
\n
\n
grep
\n
184
\n
534 KB
\n
385 KB
\n
27.8%
\n
\n
\n
cat
\n
85
\n
515 KB
\n
468 KB
\n
9.1%
\n
\n
\n
git and cargo carry the result; cat and grep are close to a no-op. OMNI\nearns its place on noisy, repetitive tooling output and gets out of the way\neverywhere else.
\n
Single fixtures from tests/fixtures/, if you want to reproduce one by hand:
\n
\n\n
\n
Command / Context
\n
Input
\n
Output
\n
Saved
\n
\n\n
\n
cargo build (large, successful)
\n
3,220 B
\n
9 B
\n
99.7%
\n
\n
\n
cargo test (490 passed, 10 failed)
\n
16.5 KB
\n
1,100 B
\n
93.3%
\n
\n
\n
pytest (failures)
\n
730 B
\n
136 B
\n
81.4%
\n
\n
\n
git status (dirty)
\n
496 B
\n
113 B
\n
77.2%
\n
\n
\n
git diff (multi-file)
\n
397 B
\n
220 B
\n
44.6%
\n
\n
\n
docker build (heavy noise)
\n
9.2 KB
\n
5.8 KB
\n
37.2%
\n
\n
\n
kubectl get pods (mixed)
\n
840 B
\n
762 B
\n
9.3%
\n
\n
\n
Latency is a real cost, not zero. OMNI runs on every hooked command, and the\nprice grows with your history: a 496-byte git status takes ~82 ms against a\nfresh database and ~308 ms against a 97 MB one. A 16.5 KB cargo test takes\n~276 ms. Budget for it.
\n
To see your own actual token savings, just run omni stats after a few days of usage.
\n\n
Quick Start & Installation
\n
Omni is incredibly easy to set up. It natively integrates into your terminal.
\n
macOS / Linux:
\n
# 1. Install via Homebrew\nbrew install fajarhide/tap/omni\n\n# 2. Setup Omni (Interactive Menu for Claude, VS Code, OpenCode, Codex, Antigravity)\nomni init\n\n# 3. Verify it's working\nomni doctor\n\n# 4. Or auto-fix any issues\nomni doctor --fix\n\n# 5. Check Current Status\nomni init --status\n
\n
Universal Installer (macOS / Linux / WSL):
\n
curl -fsSL omni.weekndlabs.com/install | bash\n
\n
Windows (PowerShell):
\n
irm omni.weekndlabs.com/install.ps1 | iex\n
\n\n
Integrations
\n
OMNI works seamlessly with the agentic tools you already use. It intercepts their terminal executions automatically.
\n
\n
Claude Code
\n
Cursor
\n
Windsurf
\n
Roo Code
\n
OpenAI Codex
\n
Antigravity CLI
\n
\n\n
Adaptive Memory OS
\n
OMNI isn't just a terminal filter—it's a cure for AI amnesia.
\n
If you've ever worked with an AI agent for more than an hour, you know the pain of context loss. You restart the agent, and suddenly it forgets what you were working on. It forgets the project goal. It starts making the exact same mistakes it made yesterday because it forgot the repository's undocumented quirks.
\n
OMNI's Memory OS runs silently in the background to solve this:
\n
\n
Stop Re-Explaining the Goal (omni goal): Set your North Star objective once. OMNI will relentlessly remind the agent of this exact priority on every single prompt, preventing it from drifting off-task.
\n
Never Lose Your Train of Thought (Session Continuity): If Cursor crashes or you switch to Claude Code, OMNI instantly injects a compressed summary of your last session. The new agent knows exactly which files were hot and what the last active error was, picking up right where you left off.
\n
Teach It Once (omni remember): Stop fixing the same hallucination. Agents can save project-specific rules, gotchas, and architecture decisions directly into OMNI's local SQLite backend. When they get stuck later, they automatically pull the exact answer back out via semantic search.
\n
\n
Your agent gets smarter about your codebase every single day, and you never have to repeat yourself again.
\n\n
How it works
\n
Omni operates purely locally using a deterministic Read → Guard → Score → Collapse → Distill → Persist pipeline.
If the AI really needs the dropped noise, OMNI's local SQLite RewindStore keeps the full uncompressed log safely hashed, allowing the agent to retrieve it anytime.
\n\n
Architecture
\n
\n \n
Built in Rust for imperceptible latency.
\n
\n
Pipeline Latency: < 10ms overhead.
\n
Memory: Operates via efficient streams, keeping memory usage flat even on 20,000-line logs.
\n
Fail Open: If OMNI panics, it fails silently and passes the raw output through. It will never crash your host agent.
\n
\n
# Development\ncargo build --release\ncargo test --all\nmake fmt && make clippy\n
\n\n
FAQ
\n
Does Omni permanently delete my logs? No. The raw logs are compressed and stored locally in the SQLite RewindStore. The AI receives a hash and can retrieve the full log if needed.
\n
Will this slow down my terminal? No. OMNI is written in Rust and executes the distillation pipeline in under 10ms.
\n
Can I add my own filters? Yes. You can teach OMNI to strip noise specific to your internal tools using TOML:
This is a passion project built for the era of Agentic AI. Whether you're here to save money on tokens, test out free models, or help build the ultimate agentic toolbelt, contributions are always welcome!
\n
\n
Development: Want to build from source? Run make ci and cargo build. Read our CONTRIBUTING.md for details.
# Install (macOS, Linux, Windows)\ncurl -sSL codecora.dev/install | sh\n\n# Store a memory\nuteke remember \"Deploy v2.1 to staging at 3pm\"\n\n# Search it back — by meaning, not just keywords\nuteke recall \"when do we deploy?\"\n
\n
That's it. No API keys. No Docker. No Python. No cloud.
\n
First run downloads the embedding model (~188MB, one-time) and you're running.
Are you an AI agent reading this? Your user just shared this repo link with you.\nRun uteke onboard to interactively configure uteke for your environment — it will\ndetect your install, ask which agent you are, toggle features, write config, and\nshow you every command available. If non-interactive: uteke onboard --yes --agent <your-agent>.
\n
\n
New to uteke? One command takes you from zero to productive:
\n
uteke onboard\n
\n
The wizard will:
\n\n
Detect if uteke is installed and if a store exists
\n
Ask which AI agent you use (Hermes, Claude, Cursor, Pi, OpenCode)
\n
Pick integration mode — manual tool calls vs automatic memory-provider
\n
Toggle features on/off (Aging, Auto-maintenance, Graph rerank, Salience/Recency boost, Server mode)
You just spent 2 hours explaining your codebase to ChatGPT. Next session? Blank slate. Again.
\n
Every AI tool forgets. Context windows fill up, sessions end, and your AI starts over every single time. Uteke gives it persistent memory — and keeps it on your machine.
\n
\n\n
\n
\n
Uteke
\n
Mnemosyne
\n
Mem0
\n
AgentMemory
\n
Letta
\n
Zep
\n
Engram
\n
\n\n
\n
Language
\n
Rust (single binary)
\n
Python (pip)
\n
Python
\n
TypeScript
\n
Python
\n
Python
\n
Go (single binary)
\n
\n
\n
Setup
\n
One binary (curl | sh)
\n
pip install + venv
\n
pip + Docker + Qdrant
\n
npm + Docker (iii-engine)
\n
pip + Docker + Postgres
\n
pip + Docker + Neo4j
\n
One binary
\n
\n
\n
API keys
\n
❌ None
\n
⚠️ For remote embeddings
\n
✅ OpenAI/LLM
\n
✅ LLM key
\n
✅ LLM key
\n
✅ LLM key
\n
❌ None
\n
\n
\n
Works offline
\n
✅ Fully
\n
⚠️ Optional
\n
❌ Cloud embedding
\n
❌ Needs LLM
\n
❌ Needs LLM
\n
❌ Needs LLM + vector DB
\n
✅ Fully
\n
\n
\n
Search
\n
Hybrid (Vector + FTS5 + RRF)
\n
sqlite-vec + FTS5
\n
Vector + Graph
\n
Vector + Graph
\n
Vector
\n
Temporal Graph
\n
FTS5 only
\n
\n
\n
Recall speed
\n
~45ms
\n
~50ms+
\n
Network round-trip
\n
Network round-trip
\n
Network round-trip
\n
Network round-trip
\n
~Fast (local)
\n
\n
\n
Multi-agent
\n
✅ Rooms (built-in collaboration)
\n
⚠️ Shared API
\n
❌
\n
❌
\n
❌
\n
❌
\n
❌
\n
\n
\n
Time-travel
\n
✅ Native point-in-time
\n
⚠️ Temporal triples
\n
❌
\n
❌
\n
❌
\n
❌
\n
❌
\n
\n
\n
MCP server
\n
✅ JSON-RPC + HTTP
\n
✅ stdio + SSE
\n
❌
\n
❌
\n
❌
\n
❌
\n
❌
\n
\n
\n
Your data
\n
✅ Never leaves machine
\n
✅ Local-first
\n
⚠️ Sent to LLM cloud
\n
⚠️ Sent to LLM cloud
\n
⚠️ Sent to LLM cloud
\n
⚠️ Sent to LLM cloud
\n
✅ Local
\n
\n
\n
License
\n
Apache 2.0
\n
MIT
\n
Apache 2.0
\n
Apache 2.0
\n
Apache 2.0
\n
Apache 2.0
\n
Apache 2.0
\n
\n
\n
\n
Uteke vs Mnemosyne: Both are local-first with semantic + FTS5 search. Mnemosyne is the closest competitor (~1.5K stars, Python). Uteke wins on single binary (no Python runtime), rooms, time-travel queries, and zero runtime dependencies.
\n
\n
\n
Uteke vs Engram: Both are single-binary, offline, no-API-key tools. But Engram is FTS5-only (keyword search). Uteke adds vector semantic search + RRF fusion + rooms + time-travel + graph relationships + smart decay + document engine + batch import. Same simplicity thesis, 10× the features.
\n
\n
\n
Uteke vs AgentMemory/Mem0/Letta/Zep: Those are powerful — but all require cloud LLM API keys and Docker infrastructure. Your data goes to OpenAI/Anthropic. Uteke runs fully offline with local ONNX embeddings. No Docker, no Python, no API keys.
\n
\n
\n \n
\n
💡 What Can You Do With Uteke?
\n
🤖 Building AI agents? Give them persistent memory without cloud dependencies. Your agent remembers user preferences, past decisions, and context — across sessions, fully offline.
\n
👥 Working in a team? Use Rooms to share knowledge. Meeting notes, project decisions, architecture choices — searchable by everyone, attributed by author.
\n
🔒 Building for privacy-sensitive domains? Healthcare, finance, legal — data stays on your machine. No API calls, no telemetry, no cloud. Local embeddings (ONNX, 768d).
\n
⌨️ Power user who lives in the terminal? Uteke is your personal knowledge graph. Remember anything, recall by meaning, link related thoughts. All from the command line.
\n\n
✨ Features
\n
Core Memory
\n
\n\n
\n
Feature
\n
What it does
\n
\n\n
\n
🧠 Hybrid Search
\n
Vector similarity + FTS5 full-text search, merged by Reciprocal Rank Fusion (RRF). Finds by meaning AND exact keywords.
\n
\n
\n
🏠 Rooms
\n
Group memories by context (meetings, projects, clients) with author attribution.
\n
\n
\n
⏳ Time-travel
\n
Recall memories as they existed at any point in time. uteke recall \"deploy\" --at 2025-01-15
\n
\n
\n
🏷️ Rich Metadata
\n
Tags, entities, categories, key:value pairs on every memory.
\n
\n
\n
🧩 Memory Types
\n
Typed categories (fact, procedure, decision, etc.) with auto-inference.
\n
\n
\n
✏️ Partial Updates
\n
Update content, tags, metadata, importance, or type without full rewrite.
\n
\n
\n
📎 Citations
\n
Source attribution on every memory (URL, file, user, import batch).
\n
\n
\n
Search & Intelligence
\n
\n\n
\n
Feature
\n
What it does
\n
\n\n
\n
🔗 Relationship Graph
\n
Link memories with typed edges (supersedes, contradicts, references). Auto-backlinks.
\n
\n
\n
🔗 Cross-Entity Linking
\n
Bidirectional memory↔document references via [[doc-slug]] wikilinks.
\n
\n
\n
🤖 Cosine Auto-Linking
\n
Automatically creates similar_to edges between related memories.
\n
\n
\n
📉 Smart Decay
\n
Composite importance scoring. Pin what matters, let stale memories fade.
\n
\n
\n
📈 Salience + Recency
\n
Dual-axis recall boost by memory type and age.
\n
\n
\n
🔍 Orphan Detection
\n
Find disconnected, low-importance memories for cleanup.
HNSW (usearch) — finds by meaning (\"deploy\" matches \"rollout\")
\n
FTS5 (SQLite) — finds by exact terms (\"deploy\" matches \"deploy\")
\n
RRF (k=60) — merges both ranked lists → best of both worlds
\n\n
Everything runs in-process. No network. No cloud. No server required (unless you want server mode).
\n
\n \n
\n
❓ FAQ
\n\nHow is Uteke different from Mem0 or Letta?
Mem0 and Letta are great — but they require cloud API keys (OpenAI/LLM) and external infrastructure (Docker, Postgres, Qdrant). Your data gets sent to a cloud LLM provider. Uteke is a single binary with zero API keys. All embeddings run locally via ONNX. Your data never leaves your machine. See comparison table.
\n\nHow is Uteke different from AgentMemory?
AgentMemory (25K stars) is a TypeScript/Node.js platform with 53 MCP tools and 12 auto-hooks. It's feature-rich but requires Docker + the iii-engine + LLM API keys. Uteke is Rust, zero dependencies, and works fully offline. If you want maximum integrations and don't mind cloud dependency → AgentMemory. If you want privacy, speed, and zero setup → Uteke.
\n\nHow is Uteke different from Engram?
Engram (2.4K stars, Go) shares our philosophy: single binary, zero deps, MCP server, local-first. The key difference is search: Engram uses FTS5 only (keyword matching). Uteke uses hybrid search (HNSW vector similarity + FTS5 + Reciprocal Rank Fusion) — meaning you can search by meaning, not just exact words. Uteke also adds rooms, time-travel, graph relationships, smart decay, document engine, and batch import.
\n\nWhat can Uteke remember?
Anything text-based: decisions, meeting notes, code snippets, project context, personal notes, agent state. You can tag, categorize, and link memories. The --batch-dir flag lets you import entire document directories.
\n\nDoes it really work offline?
Yes. The embedding model (EmbeddingGemma Q4, 768d) downloads once (~188MB) on first run. After that, zero network calls. No telemetry. If the local model fails, Uteke degrades gracefully to a no-op embedder — it never crashes and never calls a cloud API.
\n\nHow fast is recall?
~45ms as a library (measured at 100–10K memories). No network round-trip because everything is local. The LRU recall cache eliminates redundant embedding computation for repeated queries.
\n\nCan I use Uteke with my existing AI tools?
Yes. Uteke ships with an MCP server that works with Claude Code, Cursor, and Hermes. You can also use the HTTP API directly in any language. See MCP setup →
\n\nIs it production-ready?
Uteke is at v0.7.3 with 206 tests, CI/CD on every commit, and benchmark harness. It's used in production by the CodeCora team and other early adopters. Still in 0.x — expect rough edges, but the core is stable.
\n\n
🤝 Contributing
\n
cargo build --workspace # Build\ncargo test --workspace # Test (206 tests)\ncargo clippy -- -D warnings # Lint\ncargo fmt # Format\n
\n
Contributions welcome! Read CONTRIBUTING.md for the full guide.
A free, offline-first, open source Point of Sale (POS) Progressive Web App built for Indonesian Micro, Small, and Medium Enterprises (UMKM). All data is stored locally on the user's device — no server, no registration, no cost.
\n\n
✨ Features
\n
\n
POS / Cashier — Full cashier interface with cart, per-item & per-transaction discounts, payment method selection, and automatic change calculation
\n
Open Bill — Save transactions as open bills for later checkout, with customer name, table number, per-item notes, and remarks (also shown on the receipt)
\n
Multi-User Mode — Optional opt-in mode with owner + staff roles and granular per-staff permissions (e.g. manage products, view reports, do refunds). Staff log in with username + 4-6 digit PIN
\n
Multi-Language — Full Bahasa Indonesia, English, and Bahasa Malaysia translations via i18next. Language can be switched from Settings or during onboarding
\n
Responsive Layout — Mobile-first phone UI with landscape/tablet mode featuring side-by-side cashier (products + cart) and adaptive grid columns
\n
Barcode Scanning — Scan product barcodes via camera (supports EAN-13, EAN-8, UPC-A, UPC-E, Code-128, Code-39, ITF, Code-93, QR) with robust permission handling for installed PWAs, or manual keyboard entry
\n
Product Management — Complete CRUD with categories, SKU (unique & required), units, optional descriptions (searchable, previewable in cashier), photos, and barcode support
\n
Master Data Satuan (Units) — Manage units of measurement with CRUD; safe deletion blocked when in use by products
\n
Stock Management — Stock in (from suppliers) and stock out (damaged, lost, returned, etc.)
\n
Automatic COGS (HPP) — Cost of Goods Sold is automatically calculated using the weighted average method on each stock-in
\n
Sales Reports — 7/30 day sales charts, top products, total revenue & profit
\n
Transaction History — Browse completed transactions with open bill filter tabs; delete transactions with optional stock restore
\n
Supplier Management — Manage supplier contacts and details
\n
Backup & Restore — Export/import all data as JSON, with automatic backup reminders
\n
PWA — Installable to home screen, fully offline with Service Worker (Workbox), supports any orientation. Install button is also available from Settings with adaptive instructions for iOS Safari and Chrome/Edge
\n
Android APK — Ships as a native Android app via Capacitor from the same codebase, running in parallel with the PWA. Includes app icon, splash screen, and native status bar handling
\n
Bluetooth Thermal Printing — Print receipts to ESC/POS thermal printers. PWA uses Web Bluetooth (Chrome on Android); the Android APK uses Classic Bluetooth, with a configurable default printer selection (APK-only setting)
\n
Onboarding — Interactive tutorial for first-time users (the PWA install step is automatically skipped in the APK)
\n
Dark Mode — Full dark theme support
\n
Theme Customization — Pick your preferred accent color
\n
\n\n
🛠️ Tech Stack
\n
\n\n
\n
Layer
\n
Technology
\n
\n\n
\n
Framework
\n
React 18 + TypeScript
\n
\n
\n
Build Tool
\n
Vite
\n
\n
\n
Styling
\n
Tailwind CSS + shadcn/ui
\n
\n
\n
Theming
\n
next-themes (dark mode)
\n
\n
\n
Database
\n
IndexedDB via Dexie.js
\n
\n
\n
Charts
\n
Recharts
\n
\n
\n
Routing
\n
React Router DOM v6
\n
\n
\n
Forms & Validation
\n
React Hook Form + Zod
\n
\n
\n
State
\n
@tanstack/react-query
\n
\n
\n
Icons
\n
Lucide React
\n
\n
\n
i18n
\n
i18next + react-i18next
\n
\n
\n
Date
\n
date-fns (id, en-US, ms locales)
\n
\n
\n
PWA
\n
vite-plugin-pwa (Workbox)
\n
\n
\n
Barcode
\n
html5-qrcode (camera scanner + manual input)
\n
\n
\n
Receipt
\n
html2canvas (to PNG), Web Bluetooth Print (PWA), Bluetooth Classic (Android APK via Capacitor)
# Clone the repository\ngit clone https://github.com/user/kasirgratisan.git\ncd kasirgratisan\n\n# Install dependencies\nnpm install\n\n# Start the development server\nnpm run dev\n
\n
The app will be running at http://localhost:8080.
\n
Production Build (PWA/Web)
\n
npm run build\nnpm run preview\n
\n
Android Build (Capacitor)
\n
This project can also run as a native Android app using Capacitor while keeping the PWA/web version working from the same codebase.
The release AAB must be signed before uploading to Google Play. See Android signing docs.
\n
\n
Useful scripts
\n
npm run cap:sync # build web bundle and sync Capacitor\nnpm run cap:android # build, sync, then open Android Studio\nnpm run cap:run # build, sync, then run on connected Android device/emulator\n
Library Python untuk mengakses data PDDIKTI Kemdikbud dengan mudah, aman, dan terdokumentasi lengkap
\n
\n
Wrapper API Python yang powerful dan user-friendly untuk mengambil data dari PDDIKTI Kemdikbud. Library ini menyediakan interface yang mudah digunakan untuk mengakses data mahasiswa, dosen, perguruan tinggi, dan program studi di Indonesia dengan dukungan type hints, error handling yang komprehensif, dan dokumentasi lengkap.
✅ Type Hints Lengkap: Full type annotations untuk better IDE support
\n
✅ Error Handling Komprehensif: Custom exceptions dan validation
\n
✅ Context Manager Support: Resource management yang aman
\n
✅ Dokumentasi Lengkap: Google-style docstrings dengan 63 API methods
\n
✅ Performance Optimized: Connection pooling dan retry strategy
\n
✅ Indonesian Context: Field explanations dalam konteks pendidikan Indonesia
\n
✅ Flexible Parameters: Support untuk integer dan string parameters
\n
✅ Production Ready: Enhanced validation dan logging
\n
\n
📦 Instalasi
\n
pip install pddiktipy\n
\n
Requirements:
\n
\n
Python 3.7+
\n
requests
\n
urllib3
\n
\n
⚡ Quick Start
\n
from pddiktipy import api\nfrom pprint import pprint\n\n# Menggunakan context manager (recommended)\nwith api() as client:\n # Cari semua data dengan keyword\n hasil = client.search_all('Unika Soegijapranata')\n pprint(hasil)\n \n # Cari mahasiswa spesifik\n mahasiswa = client.search_mahasiswa('Ilham Riski Wibowo')\n pprint(mahasiswa)\n
\n
⚠️ Error Handling
\n
Library ini menyediakan error handling yang komprehensif:
\n
from pddiktipy import api\nfrom pddiktipy.exceptions import (\n ValidationError, \n APIConnectionError, \n APITimeoutError,\n PDDIKTIError\n)\n\ntry:\n with api() as client:\n # Ini akan raise ValidationError karena keyword kosong\n result = client.search_mahasiswa(\"\")\n \nexcept ValidationError as e:\n print(f\"Error validasi: {e}\")\nexcept APIConnectionError as e:\n print(f\"Error koneksi: {e}\")\nexcept APITimeoutError as e:\n print(f\"Request timeout: {e}\")\nexcept PDDIKTIError as e:\n print(f\"Error PDDIKTI API: {e}\")\n
\n
📚 Dokumentasi Lengkap
\n
➡️ API Documentation - 63 method API dengan dokumentasi komprehensif, contoh penggunaan, dan struktur data response
\n
📊 Struktur Data Response
\n
Semua response API menggunakan TypedDict untuk type safety dan konsistensi. Struktur data disesuaikan dengan konteks pendidikan Indonesia dan standar PDDIKTI.
\n
📝 Changelog
\n
📝 Changelog - Riwayat versi dan roadmap pengembangan
\n
📋 Requirements
\n
\n
Python 3.7+
\n
requests
\n
urllib3
\n
\n
🧪 Testing
\n
🧪 Testing Guide - Panduan testing dan quality assurance
A free, offline-first, open source Point of Sale (POS) Progressive Web App built for Indonesian Micro, Small, and Medium Enterprises (UMKM). All data is stored locally on the user's device — no server, no registration, no cost.
\n\n
✨ Features
\n
\n
POS / Cashier — Full cashier interface with cart, per-item & per-transaction discounts, payment method selection, and automatic change calculation
\n
Open Bill — Save transactions as open bills for later checkout, with customer name, table number, per-item notes, and remarks (also shown on the receipt)
\n
Multi-User Mode — Optional opt-in mode with owner + staff roles and granular per-staff permissions (e.g. manage products, view reports, do refunds). Staff log in with username + 4-6 digit PIN
\n
Multi-Language — Full Bahasa Indonesia, English, and Bahasa Malaysia translations via i18next. Language can be switched from Settings or during onboarding
\n
Responsive Layout — Mobile-first phone UI with landscape/tablet mode featuring side-by-side cashier (products + cart) and adaptive grid columns
\n
Barcode Scanning — Scan product barcodes via camera (supports EAN-13, EAN-8, UPC-A, UPC-E, Code-128, Code-39, ITF, Code-93, QR) with robust permission handling for installed PWAs, or manual keyboard entry
\n
Product Management — Complete CRUD with categories, SKU (unique & required), units, optional descriptions (searchable, previewable in cashier), photos, and barcode support
\n
Master Data Satuan (Units) — Manage units of measurement with CRUD; safe deletion blocked when in use by products
\n
Stock Management — Stock in (from suppliers) and stock out (damaged, lost, returned, etc.)
\n
Automatic COGS (HPP) — Cost of Goods Sold is automatically calculated using the weighted average method on each stock-in
\n
Sales Reports — 7/30 day sales charts, top products, total revenue & profit
\n
Transaction History — Browse completed transactions with open bill filter tabs; delete transactions with optional stock restore
\n
Supplier Management — Manage supplier contacts and details
\n
Backup & Restore — Export/import all data as JSON, with automatic backup reminders
\n
PWA — Installable to home screen, fully offline with Service Worker (Workbox), supports any orientation. Install button is also available from Settings with adaptive instructions for iOS Safari and Chrome/Edge
\n
Android APK — Ships as a native Android app via Capacitor from the same codebase, running in parallel with the PWA. Includes app icon, splash screen, and native status bar handling
\n
Bluetooth Thermal Printing — Print receipts to ESC/POS thermal printers. PWA uses Web Bluetooth (Chrome on Android); the Android APK uses Classic Bluetooth, with a configurable default printer selection (APK-only setting)
\n
Onboarding — Interactive tutorial for first-time users (the PWA install step is automatically skipped in the APK)
\n
Dark Mode — Full dark theme support
\n
Theme Customization — Pick your preferred accent color
\n
\n\n
🛠️ Tech Stack
\n
\n\n
\n
Layer
\n
Technology
\n
\n\n
\n
Framework
\n
React 18 + TypeScript
\n
\n
\n
Build Tool
\n
Vite
\n
\n
\n
Styling
\n
Tailwind CSS + shadcn/ui
\n
\n
\n
Theming
\n
next-themes (dark mode)
\n
\n
\n
Database
\n
IndexedDB via Dexie.js
\n
\n
\n
Charts
\n
Recharts
\n
\n
\n
Routing
\n
React Router DOM v6
\n
\n
\n
Forms & Validation
\n
React Hook Form + Zod
\n
\n
\n
State
\n
@tanstack/react-query
\n
\n
\n
Icons
\n
Lucide React
\n
\n
\n
i18n
\n
i18next + react-i18next
\n
\n
\n
Date
\n
date-fns (id, en-US, ms locales)
\n
\n
\n
PWA
\n
vite-plugin-pwa (Workbox)
\n
\n
\n
Barcode
\n
html5-qrcode (camera scanner + manual input)
\n
\n
\n
Receipt
\n
html2canvas (to PNG), Web Bluetooth Print (PWA), Bluetooth Classic (Android APK via Capacitor)
# Clone the repository\ngit clone https://github.com/user/kasirgratisan.git\ncd kasirgratisan\n\n# Install dependencies\nnpm install\n\n# Start the development server\nnpm run dev\n
\n
The app will be running at http://localhost:8080.
\n
Production Build (PWA/Web)
\n
npm run build\nnpm run preview\n
\n
Android Build (Capacitor)
\n
This project can also run as a native Android app using Capacitor while keeping the PWA/web version working from the same codebase.
The release AAB must be signed before uploading to Google Play. See Android signing docs.
\n
\n
Useful scripts
\n
npm run cap:sync # build web bundle and sync Capacitor\nnpm run cap:android # build, sync, then open Android Studio\nnpm run cap:run # build, sync, then run on connected Android device/emulator\n
One lightweight app. Eight features. Your whole dev workflow in a single window.
\n \n \n \n \n
\n
\n
What is TEDI?
\n
TEDI (Terminal Environment & Development Infrastructure) folds eight tools you reach for every day (a terminal, SSH client, DB browser, editor, AI agent, browser, and Git) into one window, so you stop alt-tabbing. Built on Tauri 2, so a Rust core owns every OS resource and the UI is a single webview: no Node runtime, no bundled Chromium, and a resident footprint closer to a terminal than to an IDE. No telemetry; API keys stay in the OS keychain, and it runs fully offline against a local model if you want.
\n
The eight features
\n
\n\n
\n
#
\n
Feature
\n
What it does
\n
\n\n
\n
1
\n
Terminal multiplexer
\n
Native PTY terminals (zsh / bash / fish / pwsh) on xterm.js + WebGL: split panes, tab groups, shell integration (OSC 7 / 133), inline search, and link detection. Inactive tabs keep streaming.
\n
\n
\n
2
\n
SSH connection
\n
Connect to remote hosts (russh), open remote shells, and browse/transfer files over an integrated SFTP explorer, all from a saved connection manager.
\n
\n
\n
3
\n
SQL explorer(extension)
\n
Browse and query databases from a dedicated panel. Ships as an extension (feature 8), so it installs and updates at runtime.
\n
\n
\n
4
\n
Code editor
\n
CodeMirror 6 for TS/JS, Rust, Python, PHP, HTML/CSS, JSON, Markdown, C/C++, Java, C#, SQL, and more, with inline AI autocomplete, diff view, Vim mode, and Markdown/image preview.
\n
\n
\n
5
\n
AI-native agent
\n
Bring-your-own-key agent across ten providers (OpenAI, Anthropic, Google, xAI, Cerebras, Groq, DeepSeek, SumoPod) and local models via LM Studio or any OpenAI-compatible server (Ollama, llama.cpp, vLLM). Plan mode, skills, MCP, ten sub-agents, voice input, project memory via TEDI.md, and tools gated by approval.
\n
\n
\n
6
\n
AI browser control
\n
A real in-app browser (native webview) the agent drives end to end: navigate, read, type, click, scroll, screenshot the tab to see it, and read its console errors to find out why your page broke.
\n
\n
\n
7
\n
Workspaces
\n
Each workspace keeps its own project session (tab layout + working dirs) and switches instantly. The header folder picker spawns a terminal rooted there.
\n
\n
\n
8
\n
Source control + extensions
\n
Inline Git diff / SCM pane, and a first-class extension system: install from a .zip or GitHub release to add settings, AI tools, commands, keybindings, panels, and status / header / sidebar items.
\n
\n
\n
Everything is fully themeable (presets, custom colors, transparency) while staying lightweight.
\n
Install
\n
Pre-built binaries: Releases (Windows, macOS, Linux .deb / .rpm / .AppImage). Download for your OS and install; TEDI auto-checks for updates.
\n
Screenshots
\n
\n \n \n
\n
\n \n \n
\n
\n \n
Configure AI
\n
Settings → AI, pick a provider and paste your API key. Keys go to the OS keychain via keyring, never to disk or localStorage. Full list: PROVIDERS in src/modules/ai/config.ts.
\n
Running fully local? Two routes, both keyless:
\n
\n
LM Studio is its own provider. Start its server and point TEDI at it (default http://localhost:1234/v1).
\n
OpenAI Compatible takes any server that speaks the API, and you can add several at once. Presets ship for Ollama (:11434), llama.cpp (:8080), vLLM (:8000), plus OpenRouter and 9Router. A localhost / 127.0.0.1 endpoint needs no API key; leave the field blank.
\n
\n
The same providers back inline autocomplete (Settings → AI → Autocomplete), so ghost text works on a cloud key or entirely offline. Set the model id yourself when your server names models its own way (qwen2.5-coder:7b, a GGUF filename).
\n
Extensions
\n
TEDI ships no extensions in the binary; every one (including the SQL explorer) installs at runtime. Re-installing the same manifest.id replaces the old copy, so the same path handles updates.
\n
Settings → Extensions → From file (pick a local .zip)\nSettings → Extensions → From GitHub (paste owner/repo)\nSettings → Extensions → Check updates (re-check releases/latest)\n
\n
Per-extension icon, namespaced settings/secrets/storage, and a permission-gated host API. Authoring guide: extensions/README.md. Reference extension: Discord Rich Presence.
\n
CLI
\n
tedi [PATH] # open a folder or file in TEDI\ntedi . # open the current directory\ntedi ext <subcmd> # manage extensions headlessly (install / list / update / ...)\ntedi theme <subcmd> # manage themes from the terminal\ntedi --help | --version | --update\n
\n
If TEDI is already running, the request forwards to the existing window (no second instance). On macOS / Linux AppImage the tedi command is not on PATH by default: Settings → General → \"Install tedi command in PATH\" creates a shim at ~/.local/bin/tedi. Windows' installer handles this.
\n
Architecture
\n
A Tauri 2 app: a React 19 webview (src/) talks to a Rust backend (src-tauri/) via invoke() and streaming Channels. See ARCHITECTURE.md for a one-page map, then TEDI.md for the per-module reference.
Windows: SmartScreen warns on first launch (unsigned); click More info > Run anyway. Shell priority: pwsh.exe, powershell.exe, cmd.exe.
\n
Linux: on EGL_BAD_PARAMETER or a blank window, set WEBKIT_DISABLE_DMABUF_RENDERER=1. AppImage needs FUSE (else --appimage-extract-and-run, or use the .deb / .rpm).
\n
macOS: minimum 10.15. Unsigned builds may trip Gatekeeper; drag to /Applications, run xattr -cr /Applications/TEDI.app once, then open from Finder.
\n
\n
Credits
\n
TEDI is a fork of crynta/terax-ai@v0.5.9 by Crynta. The Tauri/Rust backend, the xterm.js terminal, the CodeMirror editor, and the AI agent pipeline are the work of Crynta and the Terax contributors. Same Apache-2.0 license; if TEDI is useful, please star upstream Terax.
\n
License
\n
Apache-2.0. See LICENSE and NOTICE for required attribution.
bansos.dev adalah open-source katalog info bagi-bagi berkah, promo gratisan, dan diskonan tools coding paling legit khusus untuk developer jelata di Indonesia. Dibuat biar portofolio kita-kita tetep menyala walau dompet lagi sekarat. Nyari domain gratis, hosting free-tier, cloud credits, API credits, database gratisan, atau startup credits? Di sini tempat ngumpulnya! 100% Gratisan, No Clickbait, No Ribet. fr fr 🚀
\n
Situs ini dibangun sebagai static SvelteKit site yang super SEO-friendly, data-driven, aman di mode terang/gelap, dan gampang banget buat dikontribusikan lewat email atau merge request.
\n
Keyword cepat
\n
bansos developer, promo developer Indonesia, domain gratis, cloud credits gratis, API credits, hosting free tier, startup credits, developer tools gratis, open source Indonesia, SvelteKit static site.
\n
Fitur utama
\n
\n
Katalog bansos developer yang crawlable dan mudah dicari.
\n
Listing domain gratis, cloud gratis, hosting free-tier, API credits, database credits, dan benefit startup.
\n
Halaman detail dengan provider, benefit, syarat klaim, masa berlaku, status aktif/expired, dan link resmi.
Situs ini di-deploy dan di-hosting menggunakan Cloudflare Pages dengan adapter @sveltejs/adapter-cloudflare. Setiap kali ada merge request atau push ke branch main, Cloudflare secara otomatis memicu build dan mendistribusikan situs statis super cepat beserta seluruh dynamic OG image yang sudah di-prerender.
\n
Menjalankan proyek
\n
npm install\nnpm run dev\nnpm run build\n
\n
Validasi lokal:
\n
npm run check\nnpm run lint\n
\n
Struktur penting
\n
src/lib/data/bansos.json # data utama listing bansos\nsrc/lib/data/bansos.ts # helper selector, sorting, dan contributor stats\nsrc/lib/components/ # komponen UI reusable\nsrc/routes/list/ # halaman list dan detail bansos\nsrc/routes/contribute/ # panduan kontribusi publik\nscripts/add-bansos.mjs # script lokal tambah data\npackages/bansosdev-cli/ # CLI bansosdev (disabled untuk submit publik)\n
\n
Cara Menambah Bansos
\n
Untuk saat ini, submit publik yang aktif adalah via email dan Git clone. Jalur form, npx CLI, dan bot dinonaktifkan sementara karena spam.
\n
\n
[!TIP]\nSoon: Submisi via Discord & Telegram Bot!\nKami sedang membangun integrasi bot agar kamu bisa mengirimkan bansos baru secara otomatis langsung dari server Discord atau channel Telegram.\nSembari menunggu, yuk gabung ke komunitas kami:
\n
\n
Discord Server untuk ngobrol, diskusi, dan submit via chat (coming soon).
\n
Telegram Channel untuk dapetin update instan promo developer terbaru langsung di HP-mu.
\n
\n
\n
1. Opsi 1: Lewat Email
\n
Opsi ini sangat cocok buat kamu yang ingin berbagi info dengan cepat tanpa perlu menyentuh terminal.
Pastikan semua field penting terisi: judul, provider, benefit, syarat klaim, link resmi, status, sumber, dan kontributor.
\n\n\n
2. Opsi 2: Lewat Command Line (npx CLI) - Dinonaktifkan
\n
Submit publik via npx bansosdev add sedang dinonaktifkan sementara karena spam. Dokumentasi CLI tetap disimpan untuk maintainer dan pengujian lokal, tetapi jangan dipakai untuk submit publik saat ini.
\n
npx bansosdev add\n
\n
CLI akan menuntunmu mengisi field demi field untuk menyiapkan data lokal.
\n
Kamu juga bisa mengirimkan data langsung menggunakan argumen CLI:
Proyek bansos.dev dibangun secara gratis oleh komunitas. Jika proyek ini membantumu menghemat budget developer-mu, silakan kirim dukungan via email ke me@wau.my.id.
\n
\n
[!NOTE]\nSoon: Kami berencana menghadirkan fitur di mana donatur/pengunjung bisa mengirimkan dukungan (donasi) langsung ke masing-masing kontributor yang mendaftarkan/menulis listing bansos tersebut.
bansos.dev adalah platform komunitas open-source yang bertujuan membantu sesama developer Indonesia menemukan program bantuan sosial yang sah dan legal dari provider resmi. Kami tidak terafiliasi dengan provider mana pun.
\n
Kami dengan tegas melarang:
\n
\n
Penyalahgunaan informasi bansos untuk tujuan abuse atau mengeksploitasi celah kebijakan provider.
\n
Pelanggaran terhadap ketentuan layanan (ToS) platform atau provider pihak ketiga.
\n
Tindakan yang melanggar privasi data individu atau organisasi.
\n
Segala bentuk tindakan ilegal atau melanggar hukum yang berlaku.
\n
Submit informasi bansos yang palsu, menyesatkan, atau tidak bisa diklaim.
\n
\n
Semua informasi yang ditampilkan bersifat referensi. Selalu verifikasi langsung ke situs resmi provider sebelum melakukan klaim. Kami tidak bertanggung jawab atas perubahan kebijakan sepihak dari provider, interpretasi manfaat yang keliru, ataupun penyalahgunaan informasi oleh pihak tidak bertanggung jawab.
\n
Dengan menggunakan bansos.dev, Anda menyetujui bahwa platform ini hanyalah katalog komunitas dan segala klaim, transaksi, atau interaksi dengan provider sepenuhnya merupakan tanggung jawab pribadi masing-masing pengguna.
Unified AI coding agent platform built on Model Context Protocol (MCP) — Rust Implementation
\n
\n
Migration Status: Complete. Backend migrated from TypeScript to Rust.
\n
\n
This is the Rust implementation of masday-workflow, providing a robust, type-safe backend with the MCP protocol. The project combines a multi-agent workflow system with 4-layer memory (working, episodic, long-term, graph) and exposes MCP tools for AI agents.
# Clone and setup\ngit clone <repo-url>\ncd masday-workflow-rust\nbash scripts/setup.sh\n\n# Build Rust crates\ncargo build --workspace\n\n# Run MCP server (exposes tools via stdio, uses SQLite — no database setup needed)\ncargo run -p masday-mcp\n\n# Run API server (REST endpoints, requires PostgreSQL)\nDATABASE_URL=postgresql://USER:PASS@localhost:54341/masday_workflow \\\n cargo run -p masday-api\n\n# Build release binaries\ncargo build --release --workspace\n
\n
\n
Note: The MCP stdio server (masday-mcp) runs in SQLite-only mode — it creates ~/.masday/data.db automatically. No PostgreSQL or API server required for local use. PostgreSQL is only needed for the API server (masday-api) or remote deployments.
The masday-mcp crate exposes 70 tools in stdio/local mode (masday mcp, SQLite) and 92 tools in HTTP/remote mode (via masday-api, PostgreSQL). The per-domain counts below are the HTTP/remote superset; stdio mode registers a subset of each domain.
masday setup # Interactive setup wizard (first-time)\nmasday quickstart # One-command setup: db + migrate + install + ready\nmasday install # Install masday into current project\nmasday install --force # Force overwrite existing configs\nmasday install --standalone # Standalone mode — templates only, no build\nmasday install --remote URL # Connect to remote API server\nmasday install --skip-build # Skip cargo build, use existing binaries\nmasday uninstall # Remove masday from current project\n
\n
Update
\n
masday update # Download latest binary from GitHub Releases\n # Copies to ~/.masday/bin/, re-syncs config\n
\n
Services
\n
masday status # Check health of all services\nmasday serve # Start API server + dashboard (port 30101)\nmasday serve --port 8080 # Start on custom port\nmasday mcp # Start MCP server (stdio — used by AI platforms)\n
\n
Database
\n
masday db start # Start PostgreSQL and Redis containers\nmasday db stop # Stop all containers\nmasday db reset # Delete data and recreate containers\n
# Build\ncargo build --workspace # Build all crates\ncargo build --release # Optimized release build\ncargo build -p masday-mcp # Build specific crate\n\n# Run\ncargo run -p masday-mcp # Start MCP server\ncargo run -p masday-api # Start API server\n\n# Test\ncargo test --workspace # Run all tests\ncargo test -p masday-service # Test specific crate\ncargo test -- --nocapture # Show test output\n\n# Lint\ncargo clippy --workspace -- -D warnings # Lint with warnings as errors\ncargo fmt --all # Format code\ncargo fmt --all -- --check # Check formatting\n\n# Clean\ncargo clean # Remove build artifacts\n
\n
Release Commands
\n
# Build and release from project root (Linux + Windows)\nbash scripts/release.sh v0.3.74\n\n# Build Linux only\nbash scripts/release.sh v0.3.74 --linux-only\n\n# Test without uploading\nbash scripts/release.sh v0.3.74 --dry-run\n
\n
Release Artifacts
\n
\n\n
\n
Binary
\n
Linux
\n
Windows
\n
Size
\n
\n\n
\n
masday (CLI)
\n
masday-linux-x86_64 (39MB)
\n
masday-windows-x86_64.exe (15MB)
\n
CLI + MCP server wrapper
\n
\n
\n
masday-mcp (standalone)
\n
masday-mcp-linux-x86_64 (3.3MB)
\n
masday-mcp-windows-x86_64.exe (2.9MB)
\n
Lightweight MCP server
\n
\n
\n
\n
Note: Windows binary is built without local ONNX embeddings. Use remote embedding provider (Ollama/OpenAI) on Windows.
Local mode (default) — the MCP stdio server requires no configuration. It uses SQLite at ~/.masday/data.db automatically.
\n
Remote mode — only the API server needs env vars. MCP clients connect directly via HTTP/SSE:
\n
# ── API Server (masday-api) ──────────────────────────────\nDATABASE_URL=\"postgresql://USER:PASS@localhost:54341/masday_workflow\"\nMASDAY_API_KEY=\"your-api-key\" # Auth key for MCP clients\n\n# ── Optional (both modes) ────────────────────────────────\nRUST_LOG=\"info\" # debug, info, warn, error\nRUST_BACKTRACE=\"1\" # Enable backtrace on panic\n
\n
\n
Note: The MCP binary in local mode needs zero env vars. For remote deployments, skip the binary entirely and point MCP clients directly at the API server via HTTP/SSE.
\n
\n
MCP Stdio Binary (Zero Config)
\n
The masday-mcp binary runs standalone:
\n
\n
Database: SQLite at ~/.masday/data.db (auto-created on first run)
\n
No PostgreSQL needed for local development
\n
No API server needed — the binary contains all 20 tool domains directly
\n
\n
MCP Configuration
\n
The scripts/setup.sh script generates MCP configuration files for different platforms:
\n
\n
Claude Code: .mcp.json
\n
Gemini CLI: .gemini/settings.json
\n
VS Code Copilot: .vscode/mcp.json
\n
\n
All configurations point to the Rust MCP binary: target/debug/masday-mcp (or target/release/masday-mcp for release builds).
\n
MCP Binary Distribution
\n
The masday binary wraps the MCP server — run masday mcp to start. A separate lightweight masday-mcp binary is also available.
\n
\n
Database: SQLite at ~/.masday/data.db (auto-created on first run)
\n
No PostgreSQL needed for local development
\n
No API server needed — the binary contains all 20 tool domains directly
# Unit tests (all crates)\ncargo test --workspace\n\n# Integration tests\ncargo test --workspace --test '*_integration'\n\n# With output\ncargo test --workspace -- --nocapture\n\n# Specific test\ncargo test -p masday-service test_workflow_create\n
\n
Linting and Formatting
\n
# Format all code\ncargo fmt --all\n\n# Check formatting (CI)\ncargo fmt --all -- --check\n\n# Lint with clippy\ncargo clippy --workspace -- -D warnings\n\n# Fix clippy warnings\ncargo clippy --workspace --fix\n
\n\n
Platform Support
\n
\n\n
\n
Platform
\n
Agents
\n
Skills
\n
MCP Config
\n
Location
\n
\n\n
\n
Claude Code
\n
.claude/agents/*.md
\n
.claude/skills/*/SKILL.md
\n
.mcp.json
\n
Project root
\n
\n
\n
Gemini CLI
\n
.gemini/agents/
\n
.gemini/skills/
\n
.gemini/settings.json
\n
~/.gemini/
\n
\n
\n
VS Code Copilot
\n
.github/agents/
\n
N/A
\n
.vscode/mcp.json
\n
Project root
\n
\n
\n
OpenCode
\n
.opencode/agent/
\n
.opencode/skills/
\n
Custom
\n
~/.config/opencode/
\n
\n
\n
Run bash scripts/setup.sh to install to all platforms.
\n\n
Migration from TypeScript
\n
This project was migrated from a TypeScript monorepo to Rust. The migration is complete:
Create a feature branch (git checkout -b feat/my-feature)
\n
Follow Rust conventions:
\n
cargo fmt must pass
\n
cargo clippy must pass with no warnings
\n
Write tests (cargo test)
\n
Keep functions under 50 lines
\n
Use Result<T, E> for error handling
\n
\n
\n
Submit a pull request
\n\n
Conventions
\n
\n
Naming: snake_case for functions/modules, PascalCase for types
\n
Error Handling: thiserror for library errors, anyhow for app errors
\n
Async: Use tokio runtime, #[tokio::test] for async tests
\n
Database: sqlx compile-time checked queries only
\n
Serialization: serde derive for all types crossing boundaries
\n
\n\n
Troubleshooting
\n
Build Errors
\n
# Clear build cache\ncargo clean\n\n# Update dependencies\ncargo update\n\n# Check Rust version\nrustc --version # Should be 1.85+\n
\n
Database Connection (API Server Only)
\n
# Check PostgreSQL is running (API server mode only)\ndocker-compose ps\n\n# Check DATABASE_URL in .env\necho $DATABASE_URL\n\n# Test connection\npsql $DATABASE_URL\n
+ 
+ ![\"OMNI](\"https://raw.githubusercontent.com/fajarhide/omni/main/media/logo.png\"){kind=logo}
![\"CI\"](\"https://github.com/fajarhide/omni/actions/workflows/ci.yml/badge.svg\"){kind=icon}
![\"Release\"](\"https://img.shields.io/github/v/release/fajarhide/omni\")
![\"Rust\"](\"https://img.shields.io/badge/built_with-Rust-dca282.svg\"){kind=icon}
![\"MCP\"](\"https://img.shields.io/badge/MCP-compatible-green.svg?style=flat-square\"){kind=icon}
![\"License:](\"https://img.shields.io/github/license/fajarhide/omni\")
![\"Hits\"](\"https://hits.sh/github.com/fajarhide/omni.svg\")
![\"OMNI\"](\"https://omni.weekndlabs.com/media/performance.png\")
\n![\"OMNI](\"https://raw.githubusercontent.com/fajarhide/omni/main/media/architecture.svg\")
\n![\"Uteke](\"https://raw.githubusercontent.com/codecoradev/uteke/develop/docs/assets/uteke-banner.png\")
\n![\"CI\"](\"https://github.com/codecoradev/uteke/actions/workflows/ci.yml/badge.svg?branch=develop\"){kind=icon}
![\"Latest](\"https://img.shields.io/github/v/release/codecoradev/uteke?style=flat-square&color=green\")
![\"GitHub](\"https://img.shields.io/github/stars/codecoradev/uteke?style=flat-square&color=yellow\")
![\"License:](\"https://img.shields.io/badge/License-Apache_2.0-blue.svg?style=flat-square\"){kind=icon}
![\"Rust](\"https://img.shields.io/badge/Rust-1.75+-orange.svg?style=flat-square\"){kind=icon}
\n ![\"Docker\"](\"https://img.shields.io/badge/Docker-ready-blue.svg?style=flat-square\"){kind=icon}
![\"Recall](\"https://img.shields.io/badge/recall-~45ms-brightgreen.svg?style=flat-square\"){kind=icon}
\n![\"Uteke](\"https://raw.githubusercontent.com/codecoradev/uteke/develop/docs/assets/uteke-comparison.png\")
\n![\"Uteke](\"https://raw.githubusercontent.com/codecoradev/uteke/develop/docs/assets/uteke-architecture.png\")
\n![\"Star](\"https://img.shields.io/github/stars/codecoradev/uteke?style=social\")
\n ![\"Sumopod\"](\"https://raw.githubusercontent.com/jipraks/kasirgratisan/main/public/sponsors/sumopod.png\")
\n![\"python3.x\"](\"https://img.shields.io/badge/3.12.1-blue.svg?&logo=python&label=Python\"){kind=icon}
![\"Version](\"https://img.shields.io/pypi/v/pddiktipy?logo=Python&logoColor=white&label=PyPI&color=c125ff\")
![\"Downloads\"](\"https://img.shields.io/pepy/dt/pddiktipy?logo=PyPI&logoColor=white&label=Downloads&color=c125ff\")
![\"Author\"](\"https://img.shields.io/badge/Author-Ilham%20Riski-blue.svg?style=flat\"){kind=icon}
![\"License\"](\"https://img.shields.io/badge/License-MIT-green.svg\"){kind=icon}
![\"TEDI\"](\"https://raw.githubusercontent.com/IlhamriSKY/TEDI/main/public/icon.png\"){kind=icon}
\n ![\"license\"](\"https://img.shields.io/badge/license-Apache--2.0-green\"){kind=icon}
\n ![\"platform\"](\"https://img.shields.io/badge/platform-macOS%20%7C%20Linux%20%7C%20Windows-lightgrey\"){kind=icon}
\n ![\"no](\"https://img.shields.io/badge/runtime-no%20Electron-brightgreen\"){kind=icon}
\n ![\"no](\"https://img.shields.io/badge/telemetry-none-blue\"){kind=icon}
\n ![\"TEDI](\"https://raw.githubusercontent.com/IlhamriSKY/TEDI/main/docs/1.png\")
\n ![\"TEDI](\"https://raw.githubusercontent.com/IlhamriSKY/TEDI/main/docs/2.png\")
\n![\"TEDI](\"https://raw.githubusercontent.com/IlhamriSKY/TEDI/main/docs/3.png\")
\n ![\"TEDI](\"https://raw.githubusercontent.com/IlhamriSKY/TEDI/main/docs/4.png\")
\n![\"TEDI](\"https://raw.githubusercontent.com/IlhamriSKY/TEDI/main/docs/5.png\")
\n![\"CI\"](\"https://github.com/giosakti/duragent/actions/workflows/ci.yml/badge.svg\"){kind=icon}
![\"Docs\"](\"https://img.shields.io/badge/docs-guide-blue\"){kind=icon}
![\"Rust\"](\"https://img.shields.io/badge/rust-1.91+-orange?logo=rust\"){kind=icon}
![\"License\"](\"https://img.shields.io/badge/license-MIT-blue.svg\"){kind=icon}
![\"npm](\"https://img.shields.io/npm/v/bansosdev?label=bansosdev&color=10b981\")
![\"License:](\"https://img.shields.io/badge/License-MIT-10b981.svg\"){kind=icon}
![\"Built](\"https://img.shields.io/badge/Built%20with-SvelteKit-ff3e00\"){kind=icon}
![\"Deploy:](\"https://img.shields.io/badge/Deploy-Cloudflare%20Pages-F38020?logo=cloudflare&logoColor=white\"){kind=icon}
![\"Discord\"](\"https://img.shields.io/badge/Discord-Join%20Server-5865F2?logo=discord&logoColor=white\"){kind=icon}
![\"Telegram\"](\"https://img.shields.io/badge/Telegram-Join%20Channel-0088cc?logo=telegram&logoColor=white\"){kind=icon}
![\"WhatsApp\"](\"https://img.shields.io/badge/WhatsApp-Follow%20Channel-25D366?logo=whatsapp&logoColor=white\"){kind=icon}
![\"Bansos](\"https://raw.githubusercontent.com/wauputr4/bansos/main/static/og-banner.png\")
![\"Rust\"](\"https://img.shields.io/badge/Rust-1.85-orange?logo=rust&logoColor=white\"){kind=icon}
![\"PostgreSQL\"](\"https://img.shields.io/badge/PostgreSQL-16-4169E1?logo=postgresql&logoColor=white\"){kind=icon}
![\"MCP\"](\"https://img.shields.io/badge/MCP-1.29-green?logo=data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSIyNCIgaGVpZ2h0PSIyNCIgdmlld0JveD0iMCAwIDI0IDI0IiBmaWxsPSJub25lIiBzdHJva2U9IndoaXRlIiBzdHJva2Utd2lkdGg9IjIiPjxwYXRoIGQ9Ik0xMiAydjIwTTIgMTJoMjAiLz48L3N2Zz4=\"){kind=icon}
![\"License:](\"https://img.shields.io/badge/License-MIT-yellow.svg\"){kind=icon}