Jaseci / Jac

A programming language (Jac) + full-stack framework for building AI-integrated applications. Broader than an agent harness — it’s a language — but its distinctive features target agentic AI, so it belongs in this wiki’s framework neighbourhood.

What’s distinctive (for agents)

• Meaning Typed Programming (MTP) — you declare typed, annotated function signatures and the compiler constructs the LLM prompt from names/types/semantics, instead of hand-writing prompt strings. A different stance on the “capability as code vs. prompt” question than agent-skills (markdown procedures): here the type system is the interface to the model.
• Native graph constructs — nodes / edges / walkers for agentic workflows where an agent traverses a structured state space and calls tools — a language-level take on agent-orchestration and on the state machines behind durable-agents.
• Automatic persistence (nodes on root persist with no DB code) and scale-native deploy (identical locally on SQLite, as HTTP server, or on Kubernetes). Compiles to Python bytecode, JS, and native C-ABI.

Why it belongs here

A framework for building AI/agentic apps — the language-level end of the agent-tooling spectrum (vs. the markdown-skills + CLI-harness products elsewhere here). Its MTP and graph-walker model are a notably different design point worth tracking. (Caveat: it’s a general full-stack language, not exclusively an agent tool; placed here for its agentic constructs.)

Related

agent-orchestration · durable-agents · agent-skills · agentic-coding-harness

Re-verified 2026-08-04 — the framing changed

No version is published on the quick-guide page (jac --version is the stated check), so this pass cannot record one.

The positioning has shifted, which is the useful finding. The guide now leads with two named properties — synechic (one continuous compiler-checked medium) and topokinetic (computation moves to the data) — and the pitch “one language, one compiler, the whole stack. No glue.” That is a language-and-runtime claim aimed at eliminating context-switching between frontend, backend and deployment, addressed to founders and AI engineers.

It reframes what this page files under. The spoke recorded Jaseci as an agent framework; the project is presenting itself as a full-stack language whose agent capabilities are one use case among CLI tools and web apps. Whether that is a repositioning or always was the intent, one doc read cannot say.