Sidearm

Sidearm

WORK THAT KEEPS
ITS CONTEXT.
PERSONAL AGENTS. SHARED PROJECTS. YOUR FOUNDATION.PERSONAL · CONNECTED · UNDER YOUR CONTROL

01 / A PLACE TO KEEP GOING

One project.
Wherever the work happens.

An idea can begin in conversation, reach code, wait for a human decision and return as reviewed work. Sidearm keeps project context together on a foundation you control.

Follow the illustrative journey

Independent. Self-hosted. In active development.
Built around real projects and daily use.

02 / THE THREAD ATLAS

One project. Wherever the work happens.

A single task carries context from the first observation to human review. This scene describes an illustrative workflow, not a production interface.

Illustrative workflowThis fictional task shows how one project can carry its context.

P-41Improve the jumpProject context

CONVERSATION

Start with what feels wrong.

The project holds the observation alongside the people and tools working on it.

The jump feels too flat.

Context captured

CODING

Carry the task into code.

A connected coding session can receive shared project board and task context, then return a proposed, bounded result for review.

Inspect · change · check.

Work proposed

AUTHORITY BOUNDARY

Keep the decision with a person.

The workflow pauses at a generic approval boundary before any consequential step can continue.

Needs approval

Human decision required

HUMAN REVIEW

Bring the work back to people.

The project records a reviewable proposal, with context preserved for the next conversation.

Ready for review

Awaiting review

Conversation · P-41 carries project context.

03 / UNDER THE SURFACE

A runtime keeps authority explicit.

Sidearm is the self-hosted runtime beneath the project thread. Its layers remain separate while identity, permissions and approvals govern the actions they connect.

SIDEARM / UNDER THE SURFACE
Sidearm's conceptual layersConnections and agent work sit above runtime control. The layer descriptions explain each role. This is a conceptual illustration, not a live system or a hardware specification.SIDEARMRUNTIME CONTROL03AGENT WORKAGENT WORK02YOUR WORLDCONNECTIONS01ONE INSTANCE / THREE PERSPECTIVES
A conceptual model.
Your choice of connections.

SEPARATE LAYERS

One journey reaches different surfaces. Sidearm keeps the runtime and its authority beneath that work, where each connection remains explicit.

Meet the ecosystem

Every tool call crosses a boundary.

Identity and permissions govern actions in the runtime. Human approvals and an independent emergency stop keep authority in your hands.

  • Identity
  • Permissions
  • Approvals
IN PRACTICE

Schedule recurring work. Its tool calls still pass through the runtime’s permission checks.

Connections

Connect the places where work happens: conversations, coding clients and a browser board. Extensions add the capabilities your instance needs.

Talk through a project with Bef, then let a connected coding session work with the same board.

Agent work

Use a model or coding agent. Delegate permission-bounded research or review assignments to specialists and bring their proposals back for approval and review.

Give a specialist a bounded research or review assignment. Its permissions and required approvals remain explicit.

04 / THE ECOSYSTEM

An agent. A runtime. Room to extend.

Sidearm is the self-hosted foundation. Bef is one personal agent that uses it, and extensions add capabilities for the work at hand.

01THE EVERYDAY AGENTBefA collaborator around the work you care about.

Bef is an example personal agent using Sidearm. Its personal memory is not shared automatically; shared project board and task context travel across chat, a browser board and connected coding clients.

  • Personal context
  • Shared project work
  • Codex + Claude Code connections
02THE RUNTIMESidearmThe home that keeps an agent available.

Sidearm is the self-hosted runtime beneath personal agents and shared project work. It brings conversations, scheduled work and tools together while identity, permissions and approvals govern each action.

  • Written in Rust
  • Designed for always-on use
  • Self-hosted
03THE CAPABILITIESExtensionsBuild an instance around the work you do.

Select the connections and faculties your work needs: conversation surfaces, coding agents, memory, web tools and project tracking. Extensions operate within Sidearm’s identity and permission system.

  • Selectable capabilities
  • Shared runtime boundaries
  • A modular foundation

05 / ON THE WORKBENCH

Closer to the things you create.

Sidearm is developing a Godot connection that carries feedback and a proposed trajectory into human review. The editor change remains awaiting review.

Integration in development

Godot jump feedback in developmentA proposed jump arc and a feedback marker await human review. The drawing does not show a completed editor mutation.
P-41Improve the jumpThe apex lands too early.Awaiting human review

06 / THE PRINCIPLES

The intelligence is a choice. The agency is yours.

[ 01 ]

Own the foundation.

Run Sidearm on your own hardware. Keep the runtime, project state and personal memory under your control.

[ 02 ]

Choose what connects.

Choose your model, coding agent and capabilities. The work has a home even when your choice of intelligence changes.

[ 03 ]

Make authority explicit.

Tool calls pass through runtime permission checks. Shared projects preserve individual identity; approvals and an independent stop keep humans in control.

AGPL-3.0-ONLY

Useful tools. Explicit boundaries. Room to make them your own.