PLOWSHARE
AN OPEN-SOURCE AGENT FRAMEWORKVOL. 01 / THE POSSIBILITIES ARE YOURS

Build an agent
system of
your own.

A framework for assistants, integrations and workflows. You define the agents, connect the tools and decide how the work gets done.

INDEPENDENT BY DESIGN
Plowshare atomic-orbit and ploughshare emblem above its period lettering
YOUR MODELS. YOUR DATA.YOUR SYSTEM.
Active development · 0.1.0-SNAPSHOTApache 2.0Server-first. Remote-first.
01 / THE SYSTEMASSEMBLE A WORKING WHOLE

Give your work
a place to live.

A project brings agents, bots, tools, information, memory and workflows into a shared scope. Shape it around a research question, a codebase or an integration of your own.

FIG. A — PROJECT SCOPEDefinitions + permissions + history
A

Agents & bots

Choose prompts, models and the specialists a bot can call.

B

Tools & skills

Give each agent explicit capabilities and instructions.

C

Information

Retain sources, revisions and evidence you can inspect.

D

Memory

Carry useful lessons and earlier conversations forward.

E

Workflows

Coordinate stages with Markdown or JavaScript definitions.

F

Workspace

Connect files under declared membership and access boundaries.

The bundled definitions are starting points. Adapt them, replace them or build your own.

Definitions & grants
02 / ENGINEERING PRINCIPLETHE SERVER KEEPS THE WORK

One runtime.
Many ways in.

Use the desktop, terminal, web console or CLI. Connect external systems through SDKs and adapters. The server owns the durable work and its history.

Clients, model endpoints and the server can live on different machines. Choose your model providers and operate your own storage.

Read the architecture
FIG. B — OWNERSHIP & CONNECTIONS
DesktopTerminalWeb / CLISDK
Authenticated WebSocket operations
PLOWSHARE SERVERWork persists here.Agents · jobs · workflows · history
Model
providers
Retained
knowledge
Scoped
files
Java 21 / Spring Boot · PostgreSQL + pgvector
Authentication, uploads and Git retain their documented HTTP boundaries.
ON SCREEN / THE DESKTOP CLIENTFOLLOW THE WORK

See how the
work unfolds.

Follow model calls and tool activity in the trajectory. Select a step to inspect its input and recorded result, from the first search to the final reply.

Actual Plowshare trajectory for a public London weather and world news request. The timeline records six model calls and five search or fetch tools; a selected BBC Weather fetch displays its input and result.
ACTUAL DESKTOP VIEW · PUBLIC WEATHER & NEWS EXAMPLERecorded 4 October 2026 · tool steps selected · open image to inspect

Reference, within reach.

Install the manual into the server’s information collection, ready to read from the desktop Help view alongside retained sources.

Install the manual
Actual Plowshare desktop manual reader, showing the retained manual introduction and chapter navigation table.
ACTUAL DESKTOP VIEW · MANUAL READER DETAIL
03 / IN PRACTICEEXAMPLES TO MAKE YOUR OWN

Start with a possibility.

The same framework can serve very different work. These implemented examples show where to begin; your definitions decide what comes next.

APPLICATION NOTE / 01

From a question
to a traceable report.

The bundled research workflow retains sources, develops findings, seeks counter-evidence and assembles a draft report for review.

Inspect the evidence behind a conclusion, then use feedback to produce a new revision.

Research guide Browse workflow definitions
A RESEARCH WORKFLOW
  1. 01Frame the questionReview the objectives
  2. 02Gather & retainSources become inspectable revisions
  3. 03Test the findingsEvidence and counter-evidence
  4. 04Review the reportDraft, feedback, new revision

Requires configured search, chat and embedding services. Recorded judgments still need review.

APPLICATION NOTE / 02

Turn selected events
into an investigation.

Home Assistant owns devices and immediate automation. A Plowshare project holds the agents, scripts and knowledge used to investigate selected observations.

Configure an observed threshold and hold interval, then route qualifying events into a bounded workflow.

Home Assistant guide Explore project definitions
AN EVENT-DRIVEN PROJECT
  1. 01Observe selected statesHome Assistant WebSocket events
  2. 02Apply the route policyThreshold, hold interval and cooldown
  3. 03Investigate in a projectConfigured agents and scripts
  4. 04Return the resultConfigured report delivery

The adapter is implemented. Live device and phone acceptance remain to be verified for a deployment.

APPLICATION NOTE / 03

Let your system
work with another.

The separate A2A adapter connects external collaboration to Plowshare through its public Java SDK. Send work to a configured peer or receive supported inbound requests.

Follow durable task status and request cancellation through the documented contracts.

A2A sending A2A receiving
EXTERNAL COLLABORATION
  1. 01Configure the peerExplicit address, account and project scope
  2. 02Send or receive workSeparate adapter, public SDK
  3. 03Follow durable statusInspect the owning task
  4. 04Handle the outcomeResults and cancellation semantics

A2A supports a documented subset of operations. The Java SDK exists; remote Maven artifacts are not yet published.

04 / EXPLORE THE FRAMEWORKFOLLOW THE WORK THAT INTERESTS YOU

There’s more
to work with.

Build a knowledge practice, define your own specialists or connect an event to a repeatable procedure. Explore how the parts fit together, with practical paths into the manuals.

05 / BEGIN HEREFROM REFERENCE TO RUNNING SYSTEM

The next chapter
is yours.

Start with the manual. Set up a server, choose your models and connect a client. Then build a project around the work you want to do.

DEVELOPMENT NOTE

Plowshare is in active development at 0.1.0-SNAPSHOT. Models, tools and permissions need configuration; live workflow acceptance remains an ongoing part of the work.