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
No estimates. No backlog. No “done” without proof. Barn is a better way to plan, build and prove software.
Developer toolsHTML · CSSGitHub @rogerbarnfatherOnlineOwner 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 ↗Part of Barn.
A static site for Barn: a home page, a page for Barn itself, and one page each for Barnspec, Barnark and Barncept. There is no build step.
It leads with the philosophy and the GUIs. Details, terminology, the command
line and installation sit in each page's collapsible "Go deeper" sections.
The screenshots in assets/screens/ are real. The two Barnspec shots
(spec-map, spec-work) are the Barnspec GUI running against a copy of
Pleasant Stay, with one extra in-progress Phase added to that copy so the map
shows every status.
The others were retaken on 2026-10-25, after Barnark lost switching, files and
borrowing and Barn lost barn adopt, from the local checkouts (not yet
released) in headless Chrome at twice the size:
barn-home, ark-browse, ark-check and ark-new: a new barn made with
barn build --template="Domain Driven Design", given three contexts, two
aggregates, a Model View Controller site/ and a Library lib/StayPeriod, and
Pleasant Stay's story map copied in. The home shot hides the barn's path, which
was a scratch folder.cept-vocab (the name is kept because READMEs embed it) and cept-editor:
the Barncept GUI over a folder holding Barncept's own example concepts
(House, Room, Kitchen, Garden, Pet) and Barnark's current Domain Driven Design
template, open on House's Living room and on a bounded context's Domain.The Barnark page also describes immutable revisions of the project’s template, added on
2026-10-26. The existing ark-browse screenshot remains a Browse view; it does
not show the new History tab. The revisions are in the pushed Barncept, Barnark,
CLI, GUI and Barn main branches. These website edits are local, and the package
changes have not yet been released with new tags.
Since 2026-10-28 Barnark says "template" for every tree, the bound one too. The ark-browse,
ark-new, ark-check and barn-home screenshots, and their alt text, still say "schema", and
some show three tracked folders; retake them, alt text included, before the next release.
The three GUIs' READMEs and Barnspec's, Barnark's and Barncept's embed
spec-map, ark-browse and cept-vocab by their published URL, so replacing
one updates those READMEs too, and renaming or removing one breaks them. Their
alt text describes the picture, so it changes with it.
Open index.html in a browser, or serve the folder:
php -S localhost:8000 -t website
Each tool has one colour, shared with its GUI:
| Tool | Light | Dark |
|---|---|---|
| Barnspec (mint) | #18d19e fill, #07795f text | #3ff0bf |
| Barnark (orange) | #f25c05 fill, #c84600 text | #ff9244 |
| Barncept (sky blue) | #0b95e0 fill, #0a76b5 text | #55c9ff |
A page takes its colour from <body data-brand="spec|ark|cept">, and any
element with data-brand takes that tool's colour. The tokens are at the top
of assets/site.css.
Large and decorative text (headline accent, kickers, the "+" icons, nav hover)
uses --brand-bright; small body links keep the deeper --brand-text so they
stay readable on white.