Plan · Alpha

See the work.
Shape what comes next.

Manage projects, follow dependencies, and work with agents in context. Keep tasks, decisions, and conversations in a workspace backed by your own files.

Hanji
Ada

Start a Fieldnotes project.

Hanji

I’ll connect an outline, invitation, feedback, and publishing.

PlanCanvas
FieldnotesFieldnotes / 01

LAB-2 · Invitation

Ada

Add a warmer opening.

Claude ✳

“Welcome to Fieldnotes. Come try it.”

✓ Task complete
Chat shapes the canvas.Concept workflow · fictional data
  1. Start a Fieldnotes project.
  2. I’ll connect an outline, invitation, feedback, and publishing.
  3. Add a warmer opening.
  4. Welcome to Fieldnotes. Come try it.
  5. Task complete

Plan · A collaboration example

Turn a direction into a task someone can act on.

The team has chosen an editable starter project. Ada opens the issue in Plan and asks for help making the work precise before committing to it.

Your request
@claude clarify the acceptance criteria for this task and suggest a follow-up to test the first session.

01 · The agent contributes

A focused request carries the issue, discussion and relevant project context. The configured agent can clarify the task, suggest follow-up work and return a response attached to the issue.

02 · You review and decide

Ada reviews the criteria, decides what belongs in scope and assigns the review. The conductor can then help answer the wider question: what does this change for the rest of the project?

The resultA task with checkable criteria, an owner and a clear way to review the result.

Plan — A task with checkable criteria, an owner and a clear way to review the result.
Illustrative workflow · real interface with sample content
Read the handbook

Request access

Try Hanji with us

The Mac desktop preview is shared by invitation. Public binary downloads are not available yet. AI is optional; your provider account is managed separately.

Request access

Opens our contact form on FormSubmit.

We’ll use your details to reply to this request. Submissions are processed by FormSubmit.

Explore the interface Desktop setup guide
Already have access? Setup notes
  1. Requirements

    An existing checkout containing Plan, recent Node.js, pnpm 9.15, Git, and a C build toolchain for SQLite. You can create and browse tasks without a model account.

  2. Local setup

    From the checkout, create a fresh workspace, then a project and its first task. Keep this terminal’s workspace variable when starting the web app.

    pnpm install
    pnpm tracker init ../fieldnotes --name Fieldnotes --prefix LAB --owner ada
    export TRACKER_WORKSPACE="$(cd ../fieldnotes && pwd)"
    pnpm tracker project new fieldnotes --title Fieldnotes
    pnpm tracker new "Draft the invitation" --project fieldnotes
    pnpm dev:tracker-web
  3. First workflow

    Name your workspace, choose your products and start fresh. Hanji prepares the folders. Prefer your existing content? Connect it during setup or later.

  4. Agent connection

    The conductor is a standing conversation across all three products. Bring the page, issue or selected canvas objects into context; review requested changes and use Undo when available. Connect your own Claude or Codex setup.

See the current development status

One workspace, three views

Change the view.
Keep the same work.

Use the list to review details, the board to track status, and the canvas to understand dependencies. All three views reflect the same issues.

Plan — Actual preview interface · fictional workspace · English UIScreenshot previewPlan — Actual preview interface · fictional workspace · English UIOpen the image to view full size.
See the relationships between six issues in a fictional launch.Actual development interface · fictional data · Open full size ↗

A canvas you can follow.

Pan and zoom through grouped project territories or dependency lanes. Trace a direct link or a whole chain, pin what matters, and fit that chain into view. Parent–child relationships and blockers remain distinct.

The useful details stay close.

Open an issue alongside the work. Set its owner, status, milestone, or due date; add a comment or adjust a dependency. Saved views, filters, sortable lists, and keyboard navigation help you return to the work that matters.

People, agents, and the conversation

Ask with
the work in view.

Discuss a specific issue or start a conversation about the workspace. Address a configured Claude or Codex agent directly, with the relevant work in context.

Developer builds include ongoing Claude and Codex sessions, with permission prompts and controls to stop or continue work. These workflows are still being validated with live agents.

Example conversation with fictional participants; no live agent run.

Plan — Actual preview interface · fictional workspace · English UIScreenshot previewPlan — Actual preview interface · fictional workspace · English UIOpen the image to view full size.
Actual interface · a fictional conversation

Projects, milestones, objectives

Keep the next task
connected to the purpose.

Assign project leads, define milestones, and connect issues to key results. Review progress alongside the objectives it supports.

Plan — Actual preview interface · fictional workspace · English UIScreenshot previewPlan — Actual preview interface · fictional workspace · English UIOpen the image to view full size.
Progress, measures, and check-ins in the same workspace.Actual development interface · fictional data

Milestones grounded in the issues.

Milestones live in project documents. Linked issues supply their progress, while dates make overdue work visible. Group the canvas around a project, person, milestone, or key result.

More than a percentage.

Track metrics, completion, binary results, and rollups. Record check-ins with confidence and a note, so the reason behind a number stays visible too.

Files at the foundation

Your work.
Your agents.
Your repository.

Issues, projects, and posted comments use Markdown. Saved views use YAML. Session state and live events are stored in a local database.

The web interface, CLI, and MCP tools share the same core. Changes made through the CLI or MCP are attributed in Git. What an agent can change depends on the workflow and its permissions.

fieldnotes/
  issues/
    LAB-1.md
  projects/
    fieldnotes.md
  objectives/
    o1.md
  threads/
  views/
    launch.yml
  workspace.yml

Everyday workflow

There when
you need them.

Practical tools for navigating, organizing, and reviewing work.

Find your way through the work

Saved YAML views with names and icons. Search, persistent list sorting, and a command menu. Use J/K to move, Enter to open, V to change layout, and ? to see the available shortcuts.

Shape the workspace as you go

Create and edit projects, capture an idea, and update groups of issues. Assign an owner, priority, labels, due date, milestone, and key result without creating another source of truth.

See what needs attention

Canvas chains can reveal prerequisites outside the current view and mark cycles. The CLI’s review command groups work for a weekly review; lint flags things such as stale asks and changed or missing sources.

Connect the context

The products share your workspace identity, people, primary color and conductor. Each surface keeps the tools that fit the work.

Alpha

In active development.
Open to learning.

The Mac desktop preview is shared by invitation. Public binary downloads are not available yet. AI is optional; your provider account is managed separately.

Both Hanji projects use the AGPL-3.0-only license. Public distribution and supported installation are not yet finalized. Hosted team workspaces, individual permissions, importers, and GitHub status synchronization are not currently supported. Build automation still requires live validation before use.

Request access

Document

Give the work
something to build on.

Explore Document ↗