Key takeaways
- 0.3 second cold start, 100MB RAM — actually fast, not "fast for Electron"
- Built for the human tasks in agentic coding — managing specs, prompts, and configs while agents write code
- Free and now open source (Apache 2.0) — no account, no tracking, source on GitHub since January 2026
FAQ
What is markjason?
markjason is a native macOS app for viewing and editing .md, .json, and .env files — optimized for speed and the human tasks in AI coding workflows.
Is markjason free?
Yes. markjason is completely free with no account, no tracking, and no premium tiers.
Does markjason compete with VS Code?
Not directly. markjason is for quick file viewing/editing (0.3s launch). VS Code is a full IDE. Use markjason when you need to read a spec fast.
Is markjason an agent orchestrator?
No. markjason is a complementary tool — it handles the human tasks (specs, prompts, configs) while agents handle the code.
Is markjason open source?
Yes. The Swift source is on GitHub under the Apache 2.0 license (repo created January 2026), reversing the app's earlier closed-source distribution.
Executive Summary
markjason is a native SwiftUI app for macOS that does exactly one thing: view and edit .md, .json, and .env files extremely fast.[1] In the context of agentic coding, markjason handles "the only human tasks" — managing AGENTS.md files, editing prompts, reviewing JSON configs — while agents write the actual code.
As of June 2026, markjason is alive and actively developed. The website serves v0.34 (up from v0.26 at our original profile),[1] and the app has been open-sourced under Apache 2.0 — the Swift repo was created in January 2026 with commits through May 2026.[2]
| Attribute | Value |
|---|---|
| Company | Independent |
| Founded | 2025 |
| Funding | Not publicly disclosed (indie project; no funding announced) |
| Employees | Solo developer (GitHub: gijsverheijke)[2] |
| Headquarters | Unknown |
Product Overview
markjason is built for speed. 0.3 second cold start. 100MB RAM. Not "fast for an Electron app" — actually fast, because it's native SwiftUI.[1]
The positioning is explicit: in agentic workflows, agents write code. Humans manage the artifacts — specs, prompts, configs. markjason is optimized for those human tasks.
Key Capabilities
| Capability | Description |
|---|---|
| Instant Launch | 0.3s cold start vs VS Code's ~3s |
| Low Memory | 100MB RAM vs VS Code's 1-2GB |
| Auto-Format Detection | Paste from clipboard, auto-detects format |
| Live File Watching | External edits appear instantly |
| Collapsible JSON | Tree view with type colors, ⌘F search |
| Error Navigation | Click errors to jump to line |
| Edit/Read Toggle | ⌘E switches modes, scroll position preserved |
| Image Export | One-click export to shareable image |
| Keyboard-First | ⌘K quick open, ⌘B bold, ⌘⇧M syntax help |
| Token Counting | ⌘⇧I counts tokens for AI prompt crafting (added since v0.26)[3] |
| Outline Panel | ⌘⇧O clickable table of contents that tracks scroll position[3] |
Product Surfaces / Editions
| Surface | Description | Availability |
|---|---|---|
| macOS App | Native SwiftUI application | GA (free) |
Technical Architecture
Pure SwiftUI, no Electron, no web views.[1] This is why it's fast.
Key Technical Details
| Aspect | Detail |
|---|---|
| Deployment | Native macOS app |
| Framework | SwiftUI |
| File Types | .md, .json, .env |
| Memory | ~100MB |
| Cold Start | ~0.3s |
| Open Source | Yes — Apache 2.0, Swift source on GitHub since January 2026[2] |
| Requirements | macOS 14+ (Sonoma), universal binary (Apple Silicon + Intel)[1] |
Installation:[1] Download from markjason.sh and drag to Applications, or install via the developer's Homebrew tap.[4]
Pro tip: Right-click any .md or .json file → Get Info → Open with → markjason → Change All
Strengths
- Actually fast — 0.3s launch, 100MB RAM, native performance
- Purpose-built — Does .md/.json/.env perfectly, nothing else
- Keyboard-first — Full shortcut support for power users
- Live file watching — External edits appear without refresh
- Image export — Share specs with non-technical colleagues
- Free and open source — No account, no tracking, no premium tiers; Apache 2.0 source on GitHub[2]
- Opinionated — Won't add git, plugins, cloud sync, or light mode
Cautions
- Not an agent tool — Doesn't run or orchestrate agents
- Limited file types — Only .md, .json, .env
- Minimal traction — As of June 2026 the open-source repo has 1 star, 0 forks, and 7 open issues; we found no Hacker News or Reddit discussion of the app[2]
- macOS only — No Windows or Linux
- No collaboration — Single-user local app
- No git integration — Intentionally excluded
- Solo-developer risk — One maintainer (gijsverheijke); the app survives only as long as their interest does[2]
What Developers Say
We found no substantive community discussion of markjason as of June 11, 2026 — searches of Hacker News (Algolia), Reddit, and the broader web surfaced no threads, reviews, or user quotes about the app (HN results for "markjason" all refer to Perl author Mark Jason Dominus). For a free indie tool a few months old, silence is unsurprising, but it means adoption claims can't be independently verified: the only public signals are the website's version history and a near-zero-star GitHub repo.[2]
Pricing & Licensing
| Tier | Price | Includes |
|---|---|---|
| Free | $0 | Full functionality — "no subscription, no account required, no feature gates"[3] |
Licensing model: Free, open source (Apache 2.0)[2]
Hidden costs: None (verified against live pricing/FAQ pages, June 2026)[3]
Competitive Positioning
Direct Competitors
| Competitor | Differentiation |
|---|---|
| VS Code | VS Code is full IDE (~3s launch, 1-2GB RAM); markjason is instant viewer |
| MacDown | MacDown is markdown-focused; markjason adds JSON/env |
| Typora | Typora is paid markdown editor; markjason is free and simpler |
When to Choose markjason Over Alternatives
- Choose markjason when: You need to quickly view/edit specs, prompts, or configs
- Choose VS Code when: You need a full IDE with extensions and git
- Choose Typora when: You want a polished paid markdown writing experience
Ideal Customer Profile
Best fit:
- Developers using agentic coding workflows who manage AGENTS.md, specs, prompts
- Anyone who opens .md or .json files frequently and hates waiting
- Power users who value keyboard shortcuts and native performance
- Those who want one app for viewing agent artifacts
Poor fit:
- Anyone needing a full IDE
- Users who want git integration
- Those who need file types beyond .md/.json/.env
- Windows or Linux users
Viability Assessment
| Factor | Assessment |
|---|---|
| Financial Health | Unknown — Free product, no business model; funding not publicly disclosed |
| Market Position | Niche — Complementary tool, not primary |
| Innovation Pace | Steady — v0.34 as of June 2026 (eight point releases since our v0.26 profile in February), repo commits through May 2026[1] |
| Community/Ecosystem | Minimal — 1 GitHub star, 0 forks, no public discussion found as of June 2026[2] |
| Long-term Outlook | Neutral — Sustainable if the solo developer continues; open-sourcing reduces abandonment risk |
markjason occupies a clear niche as a fast file viewer. The risk is minimal (it's free, does one thing well, and the Apache 2.0 source means it can outlive its maintainer), but so is the upside (won't become a platform).
Bottom Line
markjason isn't an agent orchestrator — it's the tool you use alongside them. When agents are writing code and you need to quickly review a spec, edit AGENTS.md, or check a config, markjason opens in 0.3 seconds while VS Code is still loading extensions.
The opinionated approach (no git, no plugins, no cloud, dark mode only) keeps it focused. This is a single-purpose tool that does its job perfectly — and since early 2026 it's open source under Apache 2.0, removing the "can't inspect it" objection from our original profile.[2]
Recommended for: Anyone who opens .md/.json/.env files regularly and wants native Mac speed.
Not recommended for: Users needing a full editor, agent orchestration, or cross-platform support.
Outlook: A small, useful tool that fills a specific gap, still shipping steadily (v0.34, June 2026) but with essentially zero community footprint. Won't change your workflow dramatically, but removes friction from file viewing in agentic development.
Research by Ry Walker Research • methodology
Disclosure: Author is CEO of Tembo, which competes in the agent orchestration space.