Claude c60c693d13
feat(media): media job runtime, media queue and media settings
Media operations (generation, edits, transcription) need a runner that works
outside the agent turn, keeps a card in the conversation current and never
lets two processes put work on one GPU. Operations land in later commits; this
is the runtime they register with.

- Background job `media.run { jobId }` on a named `media` queue. Jobs carry an
  optional queue: the Graphile publisher passes it as queueName and the
  in-memory driver runs each queue one job at a time, in order.
- `createMediaRuntime` implements MediaRuntime (capabilities, start, get,
  cancel) over a list of `MediaOperationRegistration`s and runs jobs:
  start validates the input, creates the job and posts the bot's media card in
  one transaction (idempotent per tool call through an operation key), then
  enqueues it. The runner claims a fenced lease (an advisory lock keeps one
  live lease at a time, so the GPU stays single even when the queue is
  bypassed), renews it while polling for cancellation, writes progress and
  outputs into the card, defers with backoff when the GPU is short of memory
  or the operation asks to wait, bounds deferrals, crash restarts and run
  time, always cleans the job's temp directory and always ends the card in a
  terminal state. With continue_after the starting bot is woken in the same
  transaction that ends the job (new run trigger `media`).
- The reconciler re-enqueues jobs whose enqueue was lost, whose runner died
  or whose wait is over; a job stuck behind a dead worker's queue lock runs
  outside the queue.
- Media backends are deployment-wide settings stored encrypted as the
  `media` IntegrationProviderConfig row: `loadMediaSettings` and
  `saveMediaSettings` with the same address policy as OpenAI-compatible
  servers (no metadata hosts, public hosts only when allowed, HTTPS when a key
  is sent), a saved key never follows the settings to another server, and the
  view never returns keys. Contract in contracts/media-settings.ts.
- `createMediaOperations` is the one list both the API and the worker build
  their runtime from (empty until the operations land), and media-tools.ts has
  the shared `continue_after` schema helper for the tool definitions.
- Migration: lease, deferral, operation key and continueAfter columns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MRtGG9ARfqqhma3t85Ro2u
2026-10-03 13:31:53 +00:00
2026-09-20 17:15:16 +02:00
2026-09-20 17:15:16 +02:00

evOo

DE · Lokale Multi-Oo Programmier-Maschine — persistente KI-Teamkollegen mit Voice First, Projekt-Timeline und lokalen Tools.

EN · Local multi-Oo programming machine — persistent AI teammates with Voice First, project timeline, and local tooling.

Clean local checkout for Ingo Wagner. Brand: evOo only. Sourced from cynarAI/evoo @ f00577b (antigravity-handoff/project-timeline), with a fresh git history.

What this is / Was das ist

DE EN
Persönliche Multi-Agenten-App auf dem eigenen Rechner Personal multi-agent app on your own machine
Oos (Agents) mit Memory, Tools, Voice und Computer Oos (agents) with memory, tools, voice, and computer
Antigravity-Zukunftswerkzeuge: self_improve, autonomous-sentinel, self-update, orchestrator, local-stack, pi-local-provider, seed-ollama, Voice First / Oo-Stage Same Antigravity future tools kept on this branch

Quick start

# clone (Mac recommended path)
git clone git@github.com:cynarAI/evOo-local.git ~/Projects/evOo-local
cd ~/Projects/evOo-local

cp .env.example .env
# set POSTGRES_PASSWORD, DATABASE_URL, BETTER_AUTH_SECRET, ENCRYPTION_KEY, SCREEN_PROXY_SECRET, SANDBOX_SUPERVISOR_TOKEN

# Postgres (Compose overlay publishes 127.0.0.1:5433)
docker compose --env-file .env \
  -f infra/compose/docker-compose.yml \
  -f infra/compose/docker-compose.postgres-host.yml \
  up postgres -d

pnpm install
pnpm db:generate
pnpm db:migrate
pnpm sandbox:build   # optional, for Docker computers
pnpm dev
Service URL
Web app http://127.0.0.1:5173
API http://127.0.0.1:3100

Full local notes: docs/LOCAL-SETUP.md

Stack

  • TypeScript monorepo (pnpm + Turborepo)
  • React 19 / Vite / Tailwind (web), Electron (desktop), Expo (mobile)
  • Hono + oRPC, PostgreSQL + Prisma, Better Auth, Graphile Worker
  • Pi model routing, Docker sandboxes, Voice (Kokoro local / BYO keys)

Antigravity tools kept on this branch

  • scripts/self_improve.py
  • scripts/autonomous-sentinel.ts
  • packages/core/src/self-update.ts
  • orchestrator/ (agent_runner + agents.json)
  • apps/desktop/src/local-stack.ts
  • packages/adapters/src/pi-local-provider.ts
  • scripts/seed-ollama.ts
  • Voice First / Oo stage (apps/web CallView + stage components)

Voice (Kokoro)

Large voice model blobs are not in this repo. Recreate Kokoro separately:

docker run -p 8880:8880 ghcr.io/remsky/kokoro-fastapi-cpu:latest
export KOKORO_BASE_URL=http://127.0.0.1:8880

Details: docs/kokoro-voice.md

Tech debt (brand / packages)

Internal workspace packages still use @rakazo/* names (and some RAKAZO_* env vars). Renaming them would break the build; treat as temporary tech debt. User-facing titles and docs say evOo.

License

Apache License 2.0 — see LICENSE.

Description
evOo - Multi-Agent Orchestration Platform
Readme 24 MiB
Languages
TypeScript 94.5%
CSS 1.2%
JavaScript 1.1%
Shell 0.9%
Python 0.8%
Other 1.4%