OpenVibe.Wiki

OpenVibe.Actor

You are looking at revision 1, not the published revision 2.

Imported, written with AI assistance. Imported from the OpenVibe repository README and STATUS files at the cited commits, summarised with AI assistance; originally by OpenVibers. Not yet reviewed by a person.

OpenVibe.Actor is OpenVibe's own general agent and the router for agent work, public at openvibe.actor on port 4950. It takes a task in plain words, sends it to the best agent system for it, streams the steps, has a model of another family check the answer, and gives back the result with its cost and the reason it went where it did.

What it does

A task runs in five steps: classify it, route it with openvibe-sdk/placement over the agent catalog, run it while steps stream as events, check it with a model of another family, then deliver it or hand it on. Modes are cheapest, balanced, best, fastest and private. The OpenVibe runtime acts only through OpenVibe's public APIs: OpenVibe.Search content, OpenVibe.Tools' catalog and run API, and the Tools page reader. Private mode runs the open model on OpenVibe's own server, and the README says the task text never leaves OpenVibe. The API covers tasks, live server-sent events, cancel, a route dry run and personal agents.

What it does not do yet

Coding tasks need OpenVibe.Run sandboxes and are listed as unavailable; browser and desktop agents, more agent platforms, bring-your-own keys through OpenVibe.AI and paid tiers through OpenVibe.Billing come later. Webhooks on task state changes and an approval inbox are not finished. A project secret named by reference is refused until project secrets exist.

How it fits the network

Actor depends on OpenVibe.Network for sign-in and tokens, OpenVibe.Search and OpenVibe.Tools at runtime, and OpenVibe.Events for its two boot-time subscriptions. It calls the model providers DeepSeek and OpenAI, plus an OpenAI-compatible local server for private mode. OpenVibe.Services reads its resource index over loopback.

Status

Node 22 with Express, PostgreSQL for tasks, event logs and daily spend, and Valkey for shared limit counters. STATUS.json records it deployed; its stage is alpha. License: AGPL-3.0.

Sources

  1. OpenVibe.Actor README (commit 2c7ec5d), retrieved
    Your agent for everything: give a task in plain words, and Actor sends it to the best agent for it
  2. OpenVibe.Actor STATUS.json (commit 2c7ec5d), retrieved
    A task in plain words is classified, routed by openvibe-sdk/placement to the agent system that can do it

Inspect these sources (retrieval times, where each was first cited, what changed between revisions)

What links here

Revision 1, saved · first published · history · JSON

Discussion

Discussion is only open on public, published pages.