convez.ai
AgenteDevOps & InfraestruturaAvançado
SoloJiang

Weft

SoloJiang/weft

Orquestrador local de agentes de código com git worktrees e revisão antes do merge

Ver no GitHub
InicialPluginScore · de 0 a 100

Hub local-first de orquestração para agentes de código que gerencia projetos através de múltiplos repositórios. Divide tarefas em direções scoped e executa sessões headless de Claude Code, Codex ou OpenCode em git worktrees isoladas até gerar diffs revisáveis.

Instalação

$npx convez-ai SoloJiang/weft

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
6
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 2 meses
Versão
v0.1.0-rc.5
Issues abertas
42
Contribuidores
3

Casos de uso

  • Coordenar múltiplos agentes de IA em diferentes repositórios simultaneamente
  • Gerenciar refatorações e features complexas com aprovação controlada de escrita
  • Executar code review automatizado e pré-merge checks antes de integração

Veredito

Weft é uma solução sofisticada para equipes que precisam orquestração determinística de agentes de código com controle local completo. Ideal para projetos complexos multi-repo, mas exige familiaridade com git workflows e CLI nativo.

README

A tradução para o português deste README ainda está na fila.

Local-first delivery hub for coding agents

Give Weft one task, let a lead agent split it into scoped directions, then drive Claude Code, Codex, or OpenCode workers in isolated git worktrees until there is a reviewable diff.

Tauri v2 · React 19 · Rust · SQLite · headless agent sessions

中文说明


What Weft Is

Weft is a desktop app for running agent work across local repositories. It keeps your source on your machine, uses native CLIs rather than a remote runtime, and materializes each approved direction into its own git worktree.

The product model is:

  • Workspace: a logical set of repositories plus profiles, rules, and tools.
  • Issue: a user-facing work line for a feature, bugfix, refactor, or spike.
  • Direction: one scoped worker lane, currently with one write repository.
  • Session: one native agent session attached to a worktree.

The internal store still uses thread for the issue-level record. User-facing docs and UI call that layer an Issue.

How It Works

  1. Add or create repositories in a workspace.
  2. Start an issue and discuss the task with the lead agent.
  3. The lead proposes directions with write scope, tool choice, reason, and mandate.
  4. You approve the write declarations that should become worktrees.
  5. Workers run in headless Claude/Codex/OpenCode sessions and stream into Weft's own chat UI.
  6. Observe activity, inspect diffs, answer permission asks, and run pre-PR checks.

Product Surfaces

Workspace boardIssue board
Lead conversationRepository map

Architecture

The Rust backend owns the local SQLite store, git worktree lifecycle, headless agent processes, Ask Bridge, local MCP bus, and sidecar observation. The React frontend renders boards, chat timelines, observe/diff views, settings, and the Needs-you queue.

Current Capabilities

  • Local-first Tauri desktop app; no hosted service or account model.
  • Workspace repo add/clone/create flows with deterministic repo profiles.
  • Claude lead sessions with planner MCP and write-scope review.
  • Worker sessions for Claude Code, Codex, and OpenCode.
  • Weft-owned chat timeline with queueing, interrupt, resume, slash commands, and attachment handling.
  • Ask Bridge for tool permission requests with Allow, Always, Full, and Deny.
  • Sidecar observation for Claude jsonl, Codex rollout jsonl, and OpenCode SQLite.
  • Diff and pre-PR check surfaces from the materialized worktree.
  • Workspace and issue boards, Needs-you queue, settings, inspect views, and English/Chinese UI.

Not yet productized: automatic PR creation, protected-branch merge orchestration, CI/CD observation, team marketplace sync, and the long-running semantic Curator.

Development

npm install
npm run dev          # Vite frontend
npm run build        # TypeScript check + production frontend bundle
npm run tauri dev    # full desktop app
npm run tauri build  # release app bundle
cd src-tauri && cargo test
git diff --check

Project Layout

src/
  board/       workspace and issue boards
  session/     chat, observe, diff, permissions
  components/  shared React UI
  i18n/        English and Chinese strings
src-tauri/src/
  lead_chat/   headless agent session engine
  store/       SQLite/SeaORM entities and migrations
  bus/         local MCP/thread bus
  git.rs       repository and worktree operations
  materialize.rs
assets/
  screenshots/ README screenshots
  diagrams/    architecture and model diagrams

Design Constraints

Weft drives native CLIs through structured, headless interfaces and renders its own UI. Do not add embedded terminal/TUI dependencies for normal chat surfaces. Terminal takeover remains an escape hatch for users who want the original CLI.

Ver o original no GitHub

Bom para

Relacionados