Codync
A free, open-source 1:1 alternative to Grok Bot and Muse. Message Claude Code, Codex, Cursor and 40+ coding agents as persistent bots from your iPhone, Mac or Linux desktop. Group chats, threads, appr
Prumo starts a TypeScript project with the framework, the database rules and the test boundaries already chosen, and writes every one of them into the project.
Developer toolsTypeScript · CSSGitHub @stjosephworksOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗The public website for Prumo and Prumo Desktop, published at prumo.stjosephworks.org.
It was generated by Prumo itself, as a site project, and follows the conventions in .prumo/ like any
other generated project. That is deliberate: a tool whose answer for a public page is Next on the App
Router has no business publishing its own page on anything else.
Every document has exactly one home.
| Content | Lives in |
|---|---|
| The getting-started path, the conventions explainer, the command reference, the Desktop page | This repository, in src/app/[lang]/ |
README.md, docs/stack.md, docs/structure.md and the rest | prumo and prumo-desktop, fetched at build |
Nothing in the second row is retyped here. content/documents.json lists each one with the repository, the
path, the commit it is pinned to and the route it becomes; scripts/fetch-docs.mjs downloads exactly those
files into content/fetched/, which is not committed. A file that does not answer fails the build.
The same manifest also reads cli/package.json at that commit, so the version in the footer is the one the
pinned commit publishes rather than a number kept by hand.
There are no tags to pin to: releasing the CLI is a version bump landing on main. So the pins are commit
SHAs, raised by editing content/documents.json. That commit is also what redeploys the site, so no webhook
is needed from the other repositories.
English, Portuguese and Spanish, under /en, /pt and /es. Each language is one entry in
src/features/i18n/locales.ts, with its dictionary in
src/features/i18n/dictionaries/ and its blurb for each document in content/documents.json; the tests walk every
entry, so a new language fails them until all of it is written. Only the pages this repository writes are
translated; the fetched documents are rendered in English in every language with a note saying so, because
translating them would rebuild in other languages the duplication the manifest exists to avoid.
A path without a locale, / included, is answered by src/proxy.ts with a redirect to the visitor's language: the
one picked in the language menu, kept for a year in the locale cookie, else the first one their browser accepts
(pt-PT reaching pt), else English. A path that names a locale is never redirected.
This repository departs from prumo's rule that every file is written in English, and only there:
Portuguese and Spanish are allowed in the translated content. Every identifier, comment and commit message stays
English.
pnpm install
pnpm dev
The site runs on http://localhost:3200. / redirects to the visitor's language; see Languages.
| Command | What it does |
|---|---|
pnpm fetch:docs | Downloads the pinned documents. Runs automatically before dev, build, test and typecheck |
pnpm test | Checks the manifest, the dictionaries, and that every search anchor exists in the rendered page |
pnpm lint | Biome |
pnpm typecheck | Next's route types, then tsc --noEmit |
pnpm build · pnpm start | Production build, then serves it |
dev-logs/ holds how this site was decided, kept for context and referenced by nothing: not by this README,
not by the manifest, not by a page. Read it to understand why something is the way it is, never to learn
what is in force.