Skip to the demo workspace
HiveDev

Your software factory

Give it the task. Get on with your day.

Hive turns tasks into reviewed code with Claude Code and Codex. Built-in loops handle the review and fixes. Project memory brings what’s learned into the next task.

See the factory

From idea to reviewed pull request.

One task, carried all the way through. Select a station to look inside.

The factory floor
A request enters the line.

01 / 09 Idea

The task comes in.

A clear handoff, not another chat window.

New task

Add an agent-friendly screenshot CLI.

Upload screenshots. Read the notes. Make every command scriptable.

Screenote CLI
Project memory

Project context travels with every station.

Read by Plan

The work moves forward.
The knowledge stays with it.

ReviewFindingFixRecheck

Built-in loops

Review isn’t the finish line.

Findings go to the builder, get fixed and return for another check until the review is clean. Failing CI takes the same route.

Inspect the review loop
Project wikiSaved

Page through every screenshot.
Never silently drop notes.

↳ Used by the next plan

Self-updating memory

Your project gets wiser.

Each commit refreshes the project wiki with what changed and why. The next plan starts there, building on decisions you’ve already made.

Follow a decision into the next plan

The agents you already use

Your tools. One coordinated factory.

Pick the agent and model for each station.

In the recorded Screenote task, Claude Code and Codex both reviewed the change. Read their findings ↗

  • Claude Code
  • Codex
  • Grok
  • Pi
  • OpenCode

One real task · Screenote

It found the notes that would have gone missing.

The task: let scripts and AI agents upload screenshots to Screenote and read the notes. Hive planned the change, built it and opened the pull request.

Original request
Add a Go CLI for Screenote that is easy to install and use. The CLI should live in this repo, be written in Go, and provide a clean command surface for common Screenote workflows such as authentication/configuration, creating or uploading screenshots/notes when supported by existing APIs, listing/retrieving recent screenshots or annotations, and printing helpful errors. Design it as a small distributable binary with conventional Go module layout, tests for command parsing and API client behavior, docs in README/wiki, and an easy install path such as go install github.com/ivankuznetsov/screenote/cmd/screenote@latest plus release/package guidance. Reuse existing Screenote auth/API concepts instead of inventing a new backend contract, and keep the Rails app behavior unchanged except for any API/documentation support required by the CLI. Additional direction: design the CLI agentic-first. Agents should be the primary users, so commands must be scriptable, deterministic, composable, and friendly to non-interactive automation. Prefer structured output modes such as JSON/NDJSON where useful, stable exit codes, explicit auth/config discovery, machine-readable errors, stdin/stdout workflows, no hidden prompts unless requested, and documentation/examples aimed at coding agents and MCP/tool callers.

PR #36 Merged

Recorded run. Targeted API and Go checks passed; the full Rails suite was blocked by missing libvips. OAuth followed in PR #37.

Review → fix → recheckFrom the task history

Review pass 1 Fixed

Notes dropped after screenshot 100.

The CLI fetched only the first page. Notes on screenshot 101 and beyond disappeared without a warning.

Page through all screenshots; paginate the combined notes.

Review pass 2 Fixed

Errors that looked like success.

Rate limits, server errors and network failures were swallowed. The command returned incomplete results with exit 0.

Skip only deleted screenshots. Surface every other error.

Explore the workspace

Recorded workspace

The work is yours to inspect.

Open the original plans, changes and reviews. This is the real task history, not a simulated run.

Open the full workspace Walk through the recorded task

Board

Real tasks, from idea to completed pull request.

screenote

coding workflow
3 tasks

Inbox 0

Brainstorm 1

Plan 1

Execute 0

Open PR 0

Review 0

Artifacts 0

Finalize 0

Done 1

hive

coding workflow
9 tasks

Inbox 0

Brainstorm 1

Plan 2

Execute 0

Open PR 0

Review 1

Artifacts 0

Finalize 2

Ready to archive Updated 7d ago

This step is finished; the task has not been archived yet.

Done 3

Make room for your next idea

Let Hive take the next task.

HiveDev is the hosted version, coming soon. Join the waitlist, or run open-source Hive on your own machine today.

Install Hive

Self-host today. Get notified when hosted HiveDev is ready.

  1. 01

    Install Hive

    Start with the Hive README.

  2. 02

    Connect your repository

    Use the agents and models you already have.

  3. 03

    Hand over a task

    Come back to reviewed work and its evidence.

HiveDev, when it’s ready.

HiveDev is the hosted product being built around open-source Hive. It isn’t available yet; join the waitlist to hear when it is. We’ll use your email for HiveDev availability updates.

Read our privacy notice.