Friction

Local-first feedback for coding agents

Your agent finished the task.Friction remembers what made it harder.

Give Codex and Claude Code a private place to record recurring obstacles - then review and fix verified causes when you choose.

  • v0.1.4
  • Node.js 24+
  • MIT

The feedback loop

Keep the task moving. Keep the lesson.

  1. 01

    Work normally

    Give your agent the task. Friction stays out of the way.

  2. 02

    Capture the obstacle

    The agent leaves one short private note, then continues the main task.

  3. 03

    Review when ready

    Ask the agent to group repeats and verify likely causes against the code.

  4. 04

    Authorize one fix

    You choose the verified problem. Nothing changes without your approval.

Nothing runs in the background. Review, fixing, and sharing are separate decisions.

Capture, review, fix

Three steps. Two Agent Skills. You stay in control.

Friction gives your coding agent a short capture instruction and two reusable Agent Skills. The CLI keeps the original notes local; your agent does the reasoning.

  1. 01

    During the task

    Capture what got in the way

    A short instruction tells your agent when a problem is worth saving. It leaves one private note, then keeps working.

    Your part
    Keep working. Your agent records the note.
    What Friction uses
    CLI commandfriction add
  2. 02

    When you want the pattern

    Review with a skill

    The friction-review skill groups repeated notes and checks likely causes against the current code. It never changes anything.

    Your part
    Ask your agent to review your Friction notes.
    What Friction uses
    Agent Skillfriction-review
  3. 03

    When you approve a fix

    Fix with a skill

    The friction-fix skill works only on the verified problem you name. It fixes that scope, verifies the result, and resolves only the notes it addressed.

    Your part
    Ask your agent to fix the verified problem you name.
    What Friction uses
    Agent Skillfriction-fix

friction add is a CLI command. friction-reviewand friction-fix are Agent Skills you invoke through your agent.

Saved observations

The problems successful tasks usually hide.

Each note keeps the work, obstacle, cost, and repository context together - without collecting a transcript.

friction list - 3 open
------------------------------------------------------------------
● OPEN - 2026-08-11 14:25 UTC - fr_7e2c4a0d1b5f6c8e9a4d0f2b6c1e3a5d
repo docs-site - branch main

| While updating an already-merged documentation branch, Git refused the switch because a local README would be overwritten. This added a scoped stash, fast-forward, and restore step.

------------------------------------------------------------------
● OPEN - 2026-08-11 13:40 UTC - fr_93b7d1e4a8c2f6057b9d3e1a4c6f8b20
repo cli-tool - branch release/0.1

| While validating a release, the first full check failed after focused checks passed. This required isolated reruns to distinguish a transient suite interaction from a real regression.

------------------------------------------------------------------
● OPEN - 2026-08-11 08:53 UTC - fr_b5e1c8a4d7f20963e1b5c8a4d7f20963
repo sample-app - branch feature/setup

| While inspecting the component setup, the package runner could not write its cache in the default sandbox. This cost one failed command and an escalated retry.

Agent support

Use Friction with the coding agent you already have.

Today, Friction can set up Codex and Claude Code. Version 0.2 expands the same capture, review, and fix workflow to more agents - without adding plugins, hooks, or a background service.

Available now

Friction v0.1.4 can install its capture instruction and both skills for these coding agents.

  • CodexUser or repository

    Enable Friction across your projects or for one repository.

  • Claude CodeUser or repository

    Install the same capture, review, and fix workflow.

  • Agent SkillsReview and fix

    Use friction-review for read-only analysis. friction-fix requires an explicitly named problem.

Coming in 0.2

The next release adds setup for more agents. That setup is built and is now being tested in real sessions.

  • OpenCode and PiUser or repository

    Friction installs the instructions and skills each agent uses.

  • OpenClaw and HermesEach agent environment

    Set up each isolated agent where it actually runs.

  • WarpGuided setup

    Project setup is handled for you. User-wide setup includes one manual rule step.

  • Other coding agentsAny shell-capable agent

    Generate portable instructions when your agent is not listed yet.

The npm package is currently v0.1.4. Expanded agent setup ships with v0.2.

Private by default

Local means local.

The Friction CLI remains deterministic and model-free. This public website uses Google Tag Manager to manage site analytics; Friction does not send captured observations or CLI activity.

  • 01Local storage
  • 02No account
  • 03Public-site analytics
  • 04No background process
  • 05No transcript collection
  • 06Explicit fixes and sharing

Remote and sandboxed agents need Friction installed inside that environment. Your local private store is not uploaded or synchronized.

Changelog

Small releases, visible progress.

v0.1.4

  • Improved terminal observation cards

v0.1.3

  • Documented safe package update migration

v0.1.2

  • Clearer human-readable CLI output
Follow development on GitHub
Friction

Let completed tasks improve the next one.