About Sidecat

What Sidecat is for

Sidecat helps people and AI agents carry work forward across sessions, machines, and teams. It keeps the purpose of a task, its current state, and its results available to whoever works on it next.

These aims guide development. The contract defines Version 1 requirements; progress records what has been implemented and tested.

Continuity

A new person or agent should be able to pick up work without replaying every conversation.

Preservation

Keep requests, decisions, results, and their sources connected.

Coordination

Carry assignments, discussions, and procedures across people, agents, and machines.

Visibility

Show the goal, current progress, pending decisions, and next useful step.

Authority

Make it clear who may act, on what, and for what reason.

Intent

Connect requested actions to their purpose, instructions, and applicable rules.

Permission

Support delegation, resource limits, approval, and revocation across environments.

Federation

Cooperate across independently run nodes and organizations while each retains control of its resources and records.

Evidence

Distinguish proposals, decisions, observations, and outcomes. Let users choose stronger review and record keeping when needed.

Reuse

Once a method works, make it available beyond one agent or conversation.

Composition

Use Lisp to combine calls, save reusable routines, and run workflows that can pause and resume.

Modularity

Let independently built applications work together through published contracts, discovery, and a shared bus.

Distribution

Share applications, methods, workflows, roles, and resources through public or internal marketplaces.

Useful work

Fit the tools and practices people already use, and make the next step easier.

Adoption

Work alongside existing tools. Let people use only the parts they need.

Clarity

Make installation, calls, documentation, and recovery understandable without a private briefing.

Economics

Help teams compare approaches by time, cost, and human attention.

Improvement

Use observed results to revise or retire methods that do not help.

Where to contribute

Contribute to the shared system, build on it, or do both.

  • Improve core Sidecat: Fix a shared mechanism or an official component.
  • Build a package: Deliver an application, Lisp routine, workflow, integration, or role through the shared contracts.

Source and issues · Development and progress