Vikunja vs Linear
Side-by-side trajectory, velocity, and editorial themes.
Vikunja crossed the v1.0 finish line and pivoted hard into security hardening.
Vikunja shipped two v1.0 release candidates through late 2025 and early 2026, then jumped to a v2 series whose first widely-tagged point release, v2.2.1, is dominated by security work. The latest release patches multiple SSRF and IDOR vulnerabilities, enforces disabled/locked-account semantics across every auth surface (OIDC, API tokens, CalDAV, LDAP), and adds a shared SSRF-safe HTTP client that webhooks and migrations now route through. User-facing feature work has slowed; the visible energy is in plumbing and audit cleanup.
The arc moves from feature-completion (S3 storage, drag-and-drop project moves, hover previews in late 2025) toward platform credibility — closing security gaps a self-hosted task tool needs to clear before serious team adoption. The rapid version-number jump from v1.0.0-rc4 to v2.2.1 in two months suggests v1.0 shipped and the team tagged a v2 line aimed at addressing accumulated authz debt. Expect the next several releases to keep the security-first posture rather than return to a feature push.
The next release will likely continue closing remaining authz edges (more IDOR audits, additional credential-stripping in API responses) and bundle a translations and dependency sweep. A user-facing feature push probably waits until the security work plateaus.
Linear keeps pushing its Agent deeper — from Teams chat to MCP tools to the actual codebase.
Linear is rapidly converting itself from issue tracker into an agent-native engineering coordination layer. Every major shipment in the last month — Microsoft Teams entry point, MCP tool access, Releases tracking, and now Code Intelligence — extends what Linear Agent can reach. The traditional issue-tracking surface continues to receive steady fixes and quality-of-life work, but the strategic energy is concentrated on giving the Agent more context and more reach.
Linear is positioning its Agent as a workspace orchestrator rather than a chat assistant bolted onto issues. The progression is unmistakable: first messaging surfaces (Slack, Teams), then external tools via MCP, now the codebase itself. Each step removes a reason a user would need to leave Linear to answer a work question, and steadily makes the Agent useful to PMs, support, and sales — not just engineers writing tickets.
Expect Linear to keep widening the Agent's reach into adjacent technical surfaces — CI/CD signals, incident tools, design and data systems — and to introduce paid Agent-action tiers as usage proves out. The Code Intelligence beta will likely move to general availability with codebase-scoped permissions becoming a first-class enterprise feature.
See more alternatives to Vikunja →
See more alternatives to Linear →