Aitne vs PlanWright

Aitne and PlanWright are both productivity tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Aitne

Aitne is a local-first, open-source personal agent that runs on your machine, wakes at 04:00, pulls from your calendar, email, GitHub, and Markdown notes, and drops a one-page briefing into your Slack, Telegram, Discord, or WhatsApp DMs before your day starts. Hourly nudges surface urgent emails and pending PR reviews throughout the day. By evening it journals what actually happened, building a Markdown knowledge base you own entirely. The agent runs via npm with no cloud dependency — your data never leaves your machine. The ceiling appears fast: this is a single-user, single-machine system, and anything requiring team-wide coordination or multi-account enterprise integrations lives outside its scope.

PlanWright

PlanWright wraps Claude Code, Cursor, and Codex agents in a control plane that handles both ends of the pipeline humans haven't automated yet: turning raw meeting transcripts, Slack threads, and decks into structured, agent-claimable objectives, then triaging completed work so only judgment-bound decisions reach you. The state machine is explicit — Scheduled, In Progress, Acceptance, Done — and every lane transition produces a hash-chained, cryptographically signed audit record that the vendor describes as independently verifiable on a public trust page. Mechanical acceptance criteria clear automatically; ambiguous diffs route to a human reviewer. The audit trail is positioned directly at the SOC 2 change-approval control point. This is a cloud-only, paid product with no self-hosted option — teams with data-residency requirements hit that wall before they reach the compliance features.

Attribute	Aitne	PlanWright
Pricing	Free	Paid
Free trial	No	No
Open source	Yes	No
Has API	No	Yes
Self-hosted option	Yes	No
Platforms	macOS, Linux, Windows (Node.js-based)	Web
Pros	Runs the full agent loop — plan, act, reflect — on your local machine with no cloud dependency, which means your calendar, email, and GitHub data never transit a vendor's infrastructure. MIT-licensed and installable via npm, so you can audit, fork, and modify the scheduling logic or briefing format without waiting for a vendor roadmap. Delivers morning briefings and hourly nudges directly to Slack, Telegram, Discord, or WhatsApp, so you receive proactive context in the app you already live in rather than opening a separate dashboard. Markdown-based knowledge journaling writes outcomes to plain files you own outright, which means your daily reflections remain readable and searchable without the tool installed. GitHub integration surfaces PR reviews and repository activity in your morning brief, so pending teammate blockers do not stay invisible until standup.	Synthesizes unstructured planning inputs — transcripts, decks, Slack — into machine-claimable objectives with acceptance criteria, so agents pick up work without a human first translating chaos into task format. Acceptance triage automatically clears mechanical criteria and surfaces only judgment-bound diffs, which means a senior engineer's review time concentrates on decisions that actually require a human instead of being spread across every diff in the queue. Hash-chained, cryptographically signed audit records are produced at every state transition, so the compliance artifact SOC 2 auditors ask for exists as a byproduct of normal operation rather than a retroactive documentation effort. MCP integration lets Claude Code and Cursor agents claim objectives and record diffs directly inside the existing agent environment, so the control plane doesn't require a separate tool-switching step in the agent's workflow. The state machine enforces that no objective reaches 'Done' without a human sign-off, which means the approval gate cannot be skipped when agent output volume spikes.
Cons	Integrations are fixed at calendar, email, GitHub, and Markdown — there is no described plugin or extension layer, so the moment a team needs Jira, Linear, Notion, or Salesforce context in their briefing, they are editing the agent source directly or abandoning the tool. Single-user, single-machine architecture means there is no shared context, no team briefing, and no multi-account support; a team lead who needs their agent to coordinate across reports' calendars or repositories has no path forward here and moves to a hosted multi-user alternative. No API surface is exposed by the agent, so wiring Aitne into a broader automation stack — triggering it from CI events, reading its journal output in another system — requires direct file-system or codebase integration, which adds maintenance overhead the moment a second engineer touches it.	The product is cloud-only with no self-hosted option — teams whose security policy requires audit logs or code diffs to stay within their own infrastructure reach a hard stop before evaluating any feature; those teams move to a self-hosted alternative or build a bespoke control plane. PlanWright is designed around Claude Desktop and the Claude ecosystem via MCP; teams running agents on other orchestration stacks without Claude Desktop face an integration gap the docs do not describe a workaround for, and at sufficient agent volume they rebuild the acceptance triage logic in their existing pipeline instead. The acceptance triage is described as clearing 'mechanical criteria' automatically, but the vendor page does not define the boundary between mechanical and judgment-bound — teams with strict change-management policies that require human eyes on every diff get no throughput gain from the triage step and pay for a signed ledger they could approximate with signed commits.

Bottom line

Aitne is free while PlanWright is paid; Aitne is open source; only PlanWright exposes a public API. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between Aitne and PlanWright?

Aitne is Free and open source, while PlanWright is Paid. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Aitne better than PlanWright?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.