Jekt

Jekt is the missing context layer for software projects: durable project memory for both people and AI assistants that survives beyond any conversation “window” and serves as a complete work tracker.

Open and interoperable

A vendor-neutral specification so tools, IDEs, and AI assistants can share the same project context.

A complete tracker

Manage tickets, releases, and workflow in your repository — for many teams, a full replacement for online issue trackers.

Memory beyond the conversation

Context that survives summarization, session boundaries, and tool changes.

The Jekt™ Context Architecture

Jekt is a context architecture for software projects. It uses the repository file system as its database for both project tracking and LLM working memory.

Jekt's core insight is that tracking is a side effect of maintaining usable context. The same artifacts that help an AI assistant understand the project also serve as the project record.

Jekt stores context as human-readable files in a .jekt/ directory. Rather than simply summarizing AI conversations, Jekt preserves the semantic artifacts of the work: descriptions, plans, designs, minutes, comments, and summaries.

The Context Spectrum

Project management and AI conversation are two ends of the same context spectrum.

Project / releases
project state, delivery scope

Stories / user conversations (future)
outcomes, intent

Tickets
units of work

Semantic working context
plans, minutes, designs, TODOs, summaries

Commits
code changes

Developer–LLM conversation
current working session

Jekt surfaces and preserves the context between those ends: the working knowledge, decisions, plans, and summaries that let work be understood after the conversation has moved on.

Inside a Jekt Repository

Jekt project context is maintained as semantic artifacts in your Git repository alongside your other files.

.jekt/
└── tickets/
    └── auth-42/
        ├── description - Token Refresh.md      ← scope and intent
        ├── description.yaml                    ← status, kind, priority
        ├── minutes.md                          ← decisions and insights
        ├── plans/
        │   └── 2026-05-14-refresh-flow.md      ← implementation plan
        ├── designs/
        │   └── Token Expiration Model.md       ← durable reasoning
        ├── comments/
        │   └── 2026-05-14T18-22-00Z.md         ← discussion
        ├── summary.md                          ← what was accomplished
        └── todo - Rotate Signing Keys.md       ← deferred work

Tickets, plans, designs, minutes, comments, and summaries are stored in ordinary Markdown and YAML files. There is no separate database, no proprietary format, and no required service. The same files your IDE shows you are the files your AI assistant reads.

Jekt in Use

Using the Jekt reference prompts, adding even a small feature to your project can produce context worth keeping: why a rule exists, what was rejected, what changed, and what remains open.

You: /jekt-ticket-create let friends vote on pizza toppings

Assistant: Created [PIZZA-3] at .jekt/tickets/pizza-3/.

You: /jekt-ticket-start

Assistant: Switched to tickets/pizza-3; status started.

You: A topping with one strong dislike should be excluded, even if several people like it. Majority-only voting can still ruin the pizza for that person.

You: /jekt-minutes-update

Assistant: Appended 1 entry to .jekt/tickets/pizza-3/minutes.md. Not staged.

You: /jekt-plan-implement

Assistant: Implemented the strong-dislike exclusion rule. Nothing skipped.

You: /jekt-commit

Assistant: Committed: [PIZZA-3] Exclude strongly disliked toppings. Not pushed.

You: /jekt why can one strong dislike remove a topping?

Assistant: [PIZZA-3]'s minutes record the decision: strong dislikes exclude a topping because one unwanted topping can ruin the pizza for that person. Majority-only voting was rejected.

You: /jekt what's still open for [1.0]?

Assistant: Three tickets assigned to [1.0] are still open:

[PIZZA-3] — exclude strongly disliked toppings (started)
[PIZZA-5] — limit each person to two topping votes (not started)
[PIZZA-8] — add a final shopping list (started)

[PIZZA-2] (basic topping votes) is resolved.

Explore Jekt

Primer: Start here for an orientation to Jekt and the ideas behind it.
Specification: The normative reference: terminology, repository structure, identifiers, vocabulary, and coordination protocols.
Design Principles: The worldview that produced Jekt and the constraints that guide its evolution.
Tools: Reference prompts let you start using Jekt with GitHub Copilot in VS Code today, with a full VS Code extension coming soon.
FAQ: Common questions about setup, cost, AI use, data, and team workflows.

New to Jekt? Start with the Quickstart.