Loop Now

🤝

Build a team

Organize agents by project. Give each a model, thinking level, instructions, Skills, repositories, and tool access. Designate a Manager to coordinate the project.

🧠

Keep work in context

Continue an agent's regular conversation and workspace. Tasks use separate copies, with the same agent reusing its task workspace and session across steps.

📬

Coordinate through Inbox

Agents and people exchange messages, ask questions, and reply. Choose queue or interrupt when an agent is busy; sleeping agents can wake when messages arrive.

🔀

Run visible workflows

Follow task nodes, conditional branches, bounded review loops, retries, and saved artifacts. A task's workflow and captured configuration stay fixed after it starts.

🧩

Extend through plugins

Bring CLI and MCP tools, event hooks, accounts, permissions, and Skills into one package. Add the integrations your team needs.

🔍

See what happened

Stream replies, send images, render Markdown and Mermaid, and inspect model usage, tool commands, timing, and failures in each reply's run timeline.

From implementation to review, in one conversation

Create a Manager, a Developer, and a Reviewer. Assign their repositories, models, and allowed tools, then ask the Manager to coordinate a change:

Implement this feature, have the Reviewer check it, and return the result. Ask me through Inbox if a decision is needed.

A workflow can move from development to review and back for a bounded number of revisions. Each participant works in its task context; you can inspect messages and artifacts throughout. Your project instructions and Skills define the actual process — the platform does not prescribe a particular coding, QA, or deployment policy.

Plugins are the extension point

A plugin is one directory whose package.json is the manifest. The agent side is a standard Pi package loaded into each granted agent's Pi process; the platform side runs in a long-lived Node host next to the server, subscribing to platform events with a scoped token.

import { createDelivery, type PluginAPI } from '@loop-now/plugin-sdk'

export default function register(api: PluginAPI) {
  const delivery = createDelivery(api)
  api.on('task.completed', async (event) => {
    const { url } = api.config.get<{ url?: string }>(event.projectId)
    if (url) await delivery.deliver({ target: url, body: event, eventId: event.id, eventType: event.type })
  })
}

The manifest is authoritative: subscribing to an event, or calling an API scope, that the manifest does not declare fails — and install shows both sides, the events, and the permissions before anything runs. Read the plugin overview →

Early-stage personal edition

This project targets a single local server. The console has no login and is intended for loopback access. Credentials are stored in plaintext in the local database — protect the data directory and its backups. Model and tool providers may still receive data when you use their services.

Loop Now runs on your machine with Pi as its execution engine. You choose the models, credentials, repositories, and tools each agent may use.

Loop NowA local multi-agent workspace