Blog

Plain software, written down.

Notes on speed as respect, bringing your own agent, and refusing the AI-era pivot. From the team building Radial.

Comparisons

Free and open-source issue trackers for teams with AI agents (2026)

The best free issue tracker depends on whether you want to run a server. Sourced as of Nov 2, 2026: GitHub Issues, Plane, Gitea, Forgejo, Redmine, Taiga, OpenProject, and the free tiers of Linear and Jira, compared on free-tier limits, the true cost of self-hosting, MCP and CLI support for agents, and agent billing.

18 min read
Comparisons

The best Linear alternative in 2026, and the cheaper ones for a startup

The best Linear alternative depends on why you are leaving: Radial if coding agents do much of the work, GitHub Issues for the lowest paid price, Plane to self-host, Shortcut or Jira for a free tier or more breadth. Sourced prices as of Nov 2, 2026 for mixed human and agent teams of 5 to 200 people, whether agents are billed as seats, and the extra costs: AI credits, add-ons and self-hosting.

13 min read
Comparisons

What is a cost-effective issue tracker? Prices for 8 trackers with AI agents (2026)

A cost-effective issue tracker charges for the people, not the agents, and adds no meter. Sourced prices as of Nov 2, 2026 for Radial, Jira, Linear, GitHub Issues, Asana, ClickUp, Shortcut and Plane: free tiers, per-seat prices, agent billing, hidden costs, and the cost at 1, 10 and 25 people with agents.

17 min read
Comparisons

Jira vs Linear for AI coding agents: MCP, CLI, credits and a live claim race (2026)

Linear's MCP server lists 60 tools and scores 12.0 of 16 on agent capabilities, measured live; Jira's Rovo MCP scores 8.0 from docs, but Jira ships an official CLI (acli) and Linear does not. Neither bills agents as seats, both meter their own agents in credits, and neither has a conditional claim. Head to head with live Linear runs, Jira compared from docs, a verdict, and a third option.

26 min read
Comparisons

Radial vs Jira for coding agents: prices, MCP and CLI compared from docs (2026)

Radial is $50 per user per year, flat, with agents not billed as seats and no credits. Jira Cloud Standard is $9.70 per user per month for 1 to 100 users at its new-purchase price, or $950 a year for up to 10 users, with Rovo MCP rate-limited on Free and Rovo credits for enriched calls. Side by side, compared from docs: costs for four team sizes, agent surfaces scored on 16 shared capabilities plus 3 Radial-only ones, limits, and where Radial loses.

34 min read
Agents

How to save Claude Code and Codex session logs before they disappear

Claude Code deletes local transcripts after 30 days by default, and Codex rollouts live in one folder on one laptop. How to keep each session on the issue it worked on with Radial, how to keep them locally without a tracker, and what a scripted no-tracker baseline re-reads to resume.

15 min read
Agents

How to share an HTML prototype your coding agent built

Claude Code and Codex mock up ideas as single-file HTML. A safe way to get feedback is a link that renders the file in a sandbox next to the issue it belongs to. The options compared, the exact headers Radial sends, what they block and what they do not, and the one-command version.

12 min read
Agents

What is a software factory? And how to build one with coding agents

A software factory is a repeatable pipeline that turns intent into shipped code through fixed stations, a shared work queue and checks with evidence. With Claude Code and Codex, agents work the stations and people own the gates. What it needs, what breaks without it in a scripted test, and how to build one.

14 min read
Comparisons

The real cost of Jira: what 'industry standard' actually adds up to

Jira's sticker price is $9.70 (Standard) to $19.60 (Premium) per user per month on monthly billing for 1 to 100 users. The real cost is that plus the addons, the admin time, and now a metered AI layer. Here is the full math, and the flat alternative.

9 min read
Movement

Jira went AI-native. Developers asked for the opposite.

Atlassian shipped an AI-native Jira where every agent action is governed, measured, and tied to a business outcome. The top comment was not gratitude. Here is what developers actually want, and the pledge that says it out loud.

8 min read
Comparisons

Radial vs Shortcut: same BYO-agent thesis, a price that never moves

An honest guide to Shortcut alternatives in 2026. Where Shortcut is genuinely strong, why its agent story is already good, and the one thing a tracker building its own AI PM cannot promise you: a flat price and a written no-meter pledge.

9 min read
Changelog

The anti-roadmap: the features we will never ship

Most roadmaps are a list of what is coming. This is the opposite: the concrete list of things Radial has promised never to build, why each one is on the list, and what happens to your bill if we break the promise.

11 min read
Agents

Running agents in parallel? They need one shared record to coordinate around

Parallel agents split a job into concurrent subtasks. The hard part is not launching them, it is keeping them from stepping on each other. That is a shared-state problem, and the state your agents fight over most is the task list. Here is where it should live.

9 min read
Product

Shipped this week: deeper views, OAuth apps, webhooks, and email notifications

A week of boring-on-purpose shipping: Linear-grade view depth, third-party OAuth apps with confidential clients, HTML prototype Previews, HMAC-signed outbound webhooks, and email notifications with real preferences.

3 min read
Agents

Your background agent needs somewhere to pick up the task and file the result

A background agent is defined by two touch-points on your tracker: it picks up a task, and it files the result. Here is where that record should live so the agent can read and write it over an API.

8 min read
Engineering

Why the results appear before the spinner would: how a tracker feels instant

The trick to a fast issue tracker is not a faster server. It is keeping the working set in the client so filtering, sorting, and editing happen locally, and the network catches up in the background. Here is the architecture, and where the honest limits are.

8 min read
Engineering

GitHub stores the code, not the decision. Where the "why" should actually live.

An architecture decision record captures one significant technical choice: its context, the decision, and the consequences. Here is what an ADR is, when to write one, and why the decisions that matter most are the ones that never reach a doc/adr folder.

9 min read
Agents

Agentic coding ships the 80%. Your tracker holds the other 20%.

Agentic coding is when an AI agent plans, writes, and tests code with little human input. It ships the functional 80% fast. The durable 20%, the decisions and the record, has to live somewhere. Here is where.

8 min read
Engineering

You don't want a git issue tracker. You want issues that live next to your code.

Devs keep reinventing the git-native issue tracker: a .issues folder of Markdown committed to the repo. The instinct is right. Here is the fast, scriptable version that links branches, PRs, and commits to issues without asking you to hand-roll it.

9 min read
Agents

Your Claude Code sub-agents keep losing the thread. Give them one shared record.

Claude Code agents and agent teams are real now, but the moment you run more than one, they lose track of what the others did. Here is where the shared record should live.

8 min read
Comparisons

Graduating from Trello: when a board needs to become a system

An honest guide to Trello alternatives in 2026. Where Trello still fits, why engineering teams outgrow the board, and the case for a fast issue tracker at one flat price, agents not billed as seats.

10 min read
Agents

An issue tracker for AI agents and the humans who review them

A web board for you, the radial CLI and an MCP server for Claude Code, one shared record. The 3-command agent loop, and when Linear, Jira or Beads fit better.

13 min read
Agents

File issues from CI with the Radial CLI and --json

Turn a failed CI job into a filed issue automatically. Install the radial CLI, run radial create with --json, and pipe the returned RAD-123 identifier back into your pipeline: no dashboard, no seat cost.

8 min read
Movement

The best AI for project management isn't in the tool. It's your agent.

Every tracker is bolting on an AI copilot and a credit meter. The better AI for project management is the agent you already run, driving a fast tracker through real interfaces: agents cost $0, nothing to self-host, $50 per human per year.

7 min read
Engineering

The agile project management tool that is just a fast issue tracker

Most agile project management tools are everything-suites with a board bolted on. Here is the case for the smaller thing: a fast, scriptable issue tracker with real sprints, and nothing you have to grow into.

10 min read
Comparisons

monday makes you pre-buy AI credits. We sell one flat number.

An honest guide to monday.com alternatives in 2026: what monday is good at, when to leave, and why a dev team that just wants a fast tracker should skip the AI credit meter for one flat price, agents not billed as seats.

8 min read
Agents

Scoped API keys: one key per agent, read-only, triage-only, or full

Give each agent its own Radial API key with exactly the access it needs: read-only, triage-only, or full write. Least privilege for an agent fleet, plus how to mint, scope, and revoke keys from the CLI.

7 min read
Movement

Will your tracker still exist next year? Switching-cost anxiety, and the one-command exit

The quiet reason you stall on adopting a tracker isn't the setup. It's the fear of being stuck when it changes, gets acquired, or shuts down. Here is how to price that risk to near zero.

10 min read
Engineering

A fast board and real sprints, without the scrum tax

A scrum board is a two-dimensional view of one sprint's work: columns for status, cards for issues. Here is the version that keeps the board and the sprint and drops the ceremony, plus how to drive it from the terminal.

9 min read
Comparisons

ClickUp wants to be everything. Radial does one thing.

An honest guide to ClickUp alternatives in 2026. Where the everything-app fits, why engineering teams outgrow it, and the case for a fast tracker that does one job at one flat price, no AI meter.

10 min read
Comparisons

Project management for a 2 to 10 person startup with coding agents: cost by team size and a one-afternoon setup

For a 2 to 10 person startup whose coding agents pick up issues, use a free tier (GitHub Issues, Linear Free, Jira Free or Plane Free) until agents start racing for the same work, then a tracker with an atomic claim and agents off the seat count. Yearly cost at 2, 5 and 10 people for Jira, Linear, GitHub Issues, Plane and Radial, list prices as of Nov 2, 2026, plus a step-by-step setup and what to skip at each stage.

15 min read
Engineering

Engineering project management without the overhead

Engineering project management is planning, tracking, and shipping software work. Most tools bury that under process. Here is the lean version: a fast tracker your team runs the work in, scriptable from the terminal, with one flat price and no AI meter.

9 min read
Comparisons

Migrating from Linear to Radial: export to JSON, then radial import --from linear

How to move off Linear to Radial: export your issues to JSON, dry-run radial import --from linear, then import. Issues, projects, statuses, assignees, labels, estimates, parents, relations, comments and timestamps come across; attachments, cycles, custom fields and history do not. Plus what changes, and what stays the same.

7 min read
Comparisons

Migrating off Jira: export to JSON, then radial import --from jira

A practical guide to migrating from Jira to Radial. Export your issues to JSON, dry-run radial import --from jira, then import. Issues, statuses, priorities, assignees, labels, parents, links, comments and timestamps come across; attachments, sprints, custom fields and history do not.

7 min read
Agents

What is an MCP server? And how to point one at your issue tracker

An MCP server is the thing an AI agent connects to so it can use tools and data outside its own context. Here is what that means, how it differs from a plain API, and how to point one at your issue tracker so your agent files and closes work itself.

6 min read
Comparisons

Notion is a doc with an AI button. A tracker should stay a tracker.

An honest guide to Notion alternatives in 2026: where Notion fits, the real options for notes and wikis, and why an engineering team tracking issues in Notion should move to a dedicated tracker, one flat price, no AI meter.

9 min read
Comparisons

The best Jira alternative depends on what made you leave

The best Jira alternative in 2026 depends on why you're leaving: Linear for a lighter engineering tracker, Plane to self-host, GitHub Issues to stay in the repo, ClickUp or Monday for cross-functional teams, and Radial if coding agents do your work. Prices verified on Nov 2, 2026, and agent surfaces compared from docs.

19 min read
Movement

Which issue trackers don't charge for AI agents? A meter audit you can run today

Radial, Linear and Jira (through service accounts) document that AI agents are not billed as seats, and GitHub does not bill GitHub Apps. Only Radial also has no AI credit meter. Prices as of Nov 3, 2026 for 8 trackers plus GitHub Copilot, and a five-step meter audit with a worksheet and a script to price N humans and M agents.

16 min read
Engineering

The Linear CLI Linear never shipped: driving your tracker from the terminal

Linear has no first-party CLI, so the community built a dozen, most of them aimed at AI agents. Here is the honest roundup, and the case for a tracker that ships the command line as a first-class surface.

6 min read
Comparisons

Linear vs Jira, and the third option neither names

An honest Linear vs Jira comparison: Linear wins on speed and developer experience, Jira wins on enterprise breadth and customization. Then the question both leave open: why does the price keep moving, and where is the meter?

8 min read
Agents

Give Claude Code access to your issue tracker in 5 minutes (MCP)

Wire Claude Code to your issue tracker over MCP so your agent files, searches, and closes issues itself. A 5-minute setup, the OAuth flow, and why the durable record belongs where the agent already writes.

7 min read
Engineering

Why is Jira so slow? A field guide to the 200-requests-per-ticket problem

Jira feels slow because of how it is built: a page that fans out into dozens of round trips before it shows you a ticket. Here is what is actually happening, and what a fast tracker does instead.

7 min read
Comparisons

Radial vs Linear for coding agents: CLI, MCP, prices and a live claim race (2026)

Linear has a free tier, a hosted MCP server with 60 tools in 101 KB of schema (measured live), no official issue-management CLI, no conditional claim, and its own Linear Agent billed in AI credits. Radial is $50 per user per year, flat, with a first-party CLI, a 45-tool MCP server in 21 KB, an atomic claim, and no agent of its own. Side by side, with live Linear runs, costs for four team sizes and where Radial loses.

34 min read
Movement

Boring on purpose: the tool that disappears is the one that survives 2026

AI fatigue is now a named condition. The counter-trend is calm, durable software that gets out of the way. Here is why a boring issue tracker is the one still standing next year.

7 min read
Movement

Issue tracking isn't dead. Your tracker just got bored of you.

The most-loved issue tracker declared the category over and pivoted to agent management. The category is fine. Someone still has to keep building the fast, boring, durable thing.

6 min read