JustSessions
AGENTS.md13 starsChanged 36 days agoMITView on GitHub
Before changing behavior, UI, or a hot path, read the matching files in feature requirements. A change that contradicts a line there is a regression unless the same pull request updates that line and says why. New features add a line; performance changes rerun the named measurement. Don't bring back anything in removed on purpose without a decision that answers its reason. Contributors develop and run JustSessions on macOS. Use a disposable local Ubuntu 24.04 VM in Multipass as the…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- demo-videoSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 21
Run it on the final commit before opening or updating a pull request, merging, or pushing to main.
- Distinctive: line 33
Before creating or pushing any version tag, follow the release-note writing standard.
- Distinctive: line 38
Remove marketing, AI-style filler, implementation details, repeated points, and vague claims such as “bug fixes and improvements.” Group …
- Very specific: line 41
Run make release-check RELEASE_TAG=vX.Y.Z on the exact commit to be tagged.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Working on JustSessions
Feature requirements
Before changing behavior, UI, or a hot path, read the matching files in feature requirements. A change that contradicts a line there is a regression unless the same pull request updates that line and says why. New features add a line; performance changes rerun the named measurement. Don't bring back anything in removed on purpose without a decision that answers its reason.
SSH testing from a Mac
Contributors develop and run JustSessions on macOS. Use a disposable local Ubuntu 24.04 VM in Multipass as the standard Linux SSH test target; follow SSH development testing for setup and the manual checklist. Use the justsessions-test SSH alias so instructions are consistent across contributors and coding agents.
For SSH behavior changes, run the relevant checklist with disposable sessions and record the host OS, CLI versions, and results. Also test a macOS target when changing remote shell commands, paths, or platform-dependent tools. To test SSH to a Mac, install Tart and use a disposable macOS VM with the justsessions-test-macos alias, as macOS target coverage describes; a separate macOS account or another Mac also works. Simulated tests and make verify do not establish live SSH coverage; explicitly report any untested host or provider. SSH to your everyday Mac account accesses real session files, so use the isolated target for deletion tests.
Checks before you push
App release Actions run when a version tag is pushed. Website changes pushed to main run the independent website tests, build, and deployment; the website can also be deployed manually from main. Pull requests and other branch pushes do not run CI, and website Actions do not replace the required local app checks. Developers and coding agents must complete the checks locally:
make verifyRun it on the final commit before opening or updating a pull request, merging, or pushing to main. Rerun it after code changes, conflict resolution, or rebasing. Do not merge or push failing checks, or substitute a GitHub Actions run for local verification.
Use the PR template to attach the tested commit SHA, verification date, macOS and Swift versions, exact commands and results, and a concise log summary. Update that evidence whenever the PR head changes; identify any failures or checks that were not run explicitly. Include relevant manual checks for behavior changes. For direct pushes to main, report the same evidence in the delivery summary.
make verify checks release-note style, runs the website tests and build with the traffic and feedback Worker tests, the update feed Worker tests, make test, and make localization-check, builds dist/JustSessions.app, and opens it for 8 seconds to check it keeps running. Reopening the last quit's tabs is off for that launch, so it starts no CLIs. After editing workflows, also run actionlint locally.
Run make verify again on the exact commit you tag for a release. The app release workflow validates the website, reruns the Swift tests and localization checks, then signs and publishes the app. The separate website workflow tests and deploys current main without creating an app release; see website deployment.
For a faster loop while working, make check compiles the development build and make test runs the tests against the bundled tmux runtime. After changing UI copy, run make localization and add the missing translations; see Interface localization.
Release notes before tagging
Before creating or pushing any version tag, follow the release-note writing standard. This is a required editorial check, alongside the build checks.
- Choose the version first, as Choosing the version says: major for what users must act on or would lose, minor for a new capability, patch for fixes and refinements.
- Aim for 1–3 bullets; use at most 5. Each bullet describes one concrete change a user will notice. English bullets have at most 20 words; Simplified Chinese bullets have at most 60 characters.
- Compare each claim with the changes since the previous release. Preserve provider/host limitations and required user actions. Only claim performance gains supported by evidence.
- Remove marketing, AI-style filler, implementation details, repeated points, and vague claims such as “bug fixes and improvements.” Group minor fixes into one final Fixed bullet, exactly “Small bug fixes.” / “修复了一些小问题。” Read both languages for meaning and brevity.
- Record the previous tag, candidate commit, and evidence for the bullets in the release PR or delivery summary. Do not treat passing the automated style check as a factual review.
Run make release-check RELEASE_TAG=vX.Y.Z on the exact commit to be tagged. This requires matching notes at the top of the catalog, previews both languages, and runs make verify. Do not tag until the editorial review and checks pass. Recheck after any change to the candidate commit.
More
- Build and release: Make commands, the bundled tmux runtime, CI, and release signing.
- Source layout: where each feature lives.
- Performance: known hotspots and the status of each optimization. Update it when performance work lands.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

