Introduction

glib-code is a review-first coding workflow for shipping agent-written changes without losing control of the diff.

Agents can write code fast. The problem is not generation speed; the problem is letting generated work touch the real repo before it has been reviewed. glib-code keeps agent work isolated, turns it into a reviewable diff, and only promotes the accepted output.

System overview

flowchart TD
  User["Developer"] --> Web["Web UI"]
  User --> Desktop["Desktop app"]
  Web --> Server["glib-code server"]
  Desktop --> Server
  Server --> Provider["Provider / model"]
  Provider --> Session["Agent session"]
  Session --> Ephemeral["Ephemeral workspace"]
  Ephemeral --> Diff["Review diff"]
  Diff -->|Accept| Promote["Promote"]
  Diff -->|Revise| Session
  Promote --> Durable["Real repo"]

  classDef surface fill:#89b4fa,stroke:#74c7ec,color:#11111b,stroke-width:2px
  classDef core fill:#cba6f7,stroke:#f5c2e7,color:#11111b,stroke-width:2px
  classDef work fill:#f9e2af,stroke:#fab387,color:#11111b,stroke-width:2px
  classDef safe fill:#a6e3a1,stroke:#94e2d5,color:#11111b,stroke-width:2px

  class Web,Desktop surface
  class Server,Provider,Session core
  class Ephemeral,Diff work
  class Promote,Durable safe

What glib-code gives you

• A session boundary for every agent task.
• Provider/model selection that is explicit instead of ambient.
• Reviewable diffs before changes are promoted.
• A clean handoff from isolated work to the real workspace.
• Surfaces for web, server, and desktop workflows.

Mental model

1. Start a session from a real project state.
2. Let the agent work in isolation.
3. Review the resulting diff.
4. Promote only the changes you accept.
5. Keep the durable repo clean.

Where to go next

• Why glib-code explains the problem it solves.
• Review-first loop covers the core workflow.
• Sessions explains the unit of agent work.
• Web, Server, and Desktop cover the three surfaces.