J
juxt-lang/juxt
Juxt-lang: a language for directing AI agents
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Official descriptionJuxt-lang: a language for directing AI agents. Many minds, one intent. Created by Amit N.
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"juxt-lang-juxt": {
"command": "npx",
"args": ["juxt-lang"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"juxt-lang-juxt": {
"command": "npx",
"args": ["juxt-lang"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio juxt-lang-juxt -- npx juxt-lang
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 1 ★ · juxt-lang/juxt · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-24 · last seen 2026-11-14 · seen 25× · listed by 2 sources
- Score
- score 203 · 1 ★ · 2 sources · repo
- Install
npx juxt-lang
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx juxt-lang. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
juxt-lang/juxt；first catalogued 2026-10-24；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.Created by Amit N · Contact
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Website ·
Quick start ·
Language ·
Examples ·
Roadmap ·
Discussions
▶ Watch the films · a narrated guide and the hand-drawn launch film, both animated in code
Juxt-lang is a language for directing AI agents. You put many models side by side, give them one intent, and get the full strength of each, without the guessing.
You never have to learn it. Add two words to a normal request and your coding agent compiles it into a short, reviewable program before it writes any code. The program holds the objective, the rules, the questions it would otherwise guess, and the checks that prove the work is done.
text
you › use juxt: add a cancel-order endpoint, refunds go back to the card
Understood as
objective POST /orders/{id}/cancel, refund to the original card
MUST idempotent writes (a retried cancel never refunds twice)
verify cancel twice -> 1 refund · shipped order -> 409
OPEN cancel after shipping? partial refunds?
## Why Juxt
| The problem with agents today | What Juxt does |
| Agents guess at unclear requirements and you find out in review | Unclear points become OPEN questions, asked before any code is written |
| House rules live in people's heads or in long prompts | Rules are MUST / MUST NOT lines that outrank the objective and are checked by a fresh reviewer |
| "Done" means "it compiled" | Every program carries verify checks that must pass |
| Each tool (Claude Code, Codex, CI) needs its own prompting | One program, compiled to each harness's native skills, commands and subagents |
| The same status questions are re-asked of a model every day | Digests and status updates come from git, with citations; repeat asks are served from cache |
| Nobody can audit why an agent did what it did | Programs are plain-text .juxt files in your repo, versioned and reviewable like code |
## How Juxt compares
| | Juxt | GitHub Spec Kit | Kiro | AGENTS.md |
| Format | Formal grammar, typed IR, JSON Schema | Markdown per phase | Markdown: EARS requirements, design, tasks | Free-form Markdown |
| Checks | lint, validate, drift check in CI | Checklists; CI gates via extensions | Manual review | None defined |
| Maturity | Early (0.7), few users | Widely adopted | AWS product | De facto standard |
The others are ahead on maturity, integrations and ecosystem. Juxt's difference is a program you can check mechanically and a build that fails on drift. They work together: AGENTS.md describes the repo, a .juxt program states one change and how to prove it. Full comparison: juxt-lang.github.io/#/home/compare.
## Does it help? Measure it
bench/ runs the same agent on the same tasks with and without Juxt, scores them with hidden acceptance tests, and records the agent's own token usage and cost. No results are claimed yet; they will be published unedited, losses included.
## How it works
mermaid
flowchart LR
A["Plain request 'use juxt: …'"] --> B["Compile objective · rules · contract"]
B --> C{"OPEN questions?"}
C -- yes --> D["Ask you"] --> B
C -- no --> E["Build native skills and subagents"]
E --> F["Verify tests + fresh reviewer vs every MUST"]
F --> G["juxt/.juxt saved in git"]
A compiled program is short and readable (examples/cancel-order.juxt):
Quick start ·
Language ·
Examples ·
Roadmap ·
Discussions
▶ Watch the films · a narrated guide and the hand-drawn launch film, both animated in code
Juxt-lang is a language for directing AI agents. You put many models side by side, give them one intent, and get the full strength of each, without the guessing.
You never have to learn it. Add two words to a normal request and your coding agent compiles it into a short, reviewable program before it writes any code. The program holds the objective, the rules, the questions it would otherwise guess, and the checks that prove the work is done.
text
you › use juxt: add a cancel-order endpoint, refunds go back to the card
Understood as
objective POST /orders/{id}/cancel, refund to the original card
MUST idempotent writes (a retried cancel never refunds twice)
verify cancel twice -> 1 refund · shipped order -> 409
OPEN cancel after shipping? partial refunds?
## Why Juxt
| The problem with agents today | What Juxt does |
| Agents guess at unclear requirements and you find out in review | Unclear points become OPEN questions, asked before any code is written |
| House rules live in people's heads or in long prompts | Rules are MUST / MUST NOT lines that outrank the objective and are checked by a fresh reviewer |
| "Done" means "it compiled" | Every program carries verify checks that must pass |
| Each tool (Claude Code, Codex, CI) needs its own prompting | One program, compiled to each harness's native skills, commands and subagents |
| The same status questions are re-asked of a model every day | Digests and status updates come from git, with citations; repeat asks are served from cache |
| Nobody can audit why an agent did what it did | Programs are plain-text .juxt files in your repo, versioned and reviewable like code |
## How Juxt compares
| | Juxt | GitHub Spec Kit | Kiro | AGENTS.md |
| Format | Formal grammar, typed IR, JSON Schema | Markdown per phase | Markdown: EARS requirements, design, tasks | Free-form Markdown |
| Checks | lint, validate, drift check in CI | Checklists; CI gates via extensions | Manual review | None defined |
| Maturity | Early (0.7), few users | Widely adopted | AWS product | De facto standard |
The others are ahead on maturity, integrations and ecosystem. Juxt's difference is a program you can check mechanically and a build that fails on drift. They work together: AGENTS.md describes the repo, a .juxt program states one change and how to prove it. Full comparison: juxt-lang.github.io/#/home/compare.
## Does it help? Measure it
bench/ runs the same agent on the same tasks with and without Juxt, scores them with hidden acceptance tests, and records the agent's own token usage and cost. No results are claimed yet; they will be published unedited, losses included.
## How it works
mermaid
flowchart LR
A["Plain request 'use juxt: …'"] --> B["Compile objective · rules · contract"]
B --> C{"OPEN questions?"}
C -- yes --> D["Ask you"] --> B
C -- no --> E["Build native skills and subagents"]
E --> F["Verify tests + fresh reviewer vs every MUST"]
F --> G["juxt/.juxt saved in git"]
A compiled program is short and readable (examples/cancel-order.juxt):
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/juxt-lang-juxt/)
- Source
- github · https://github.com/juxt-lang/juxt
- Browse by field
- Agent skills
- Traction
- 1 ★
- Listed by
- 2 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.