openclaw/lobster

Lobster is a Openclaw-native workflow shell: a typed, local-first “macro engine” that turns skills/tools into composable pipelines and safe automations—and...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 19 minutes ago
Added to GitGenius on April 28th, 2026
Created on January 18th, 2026
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 289
Total Stargazers: 1,263 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.0 days
Mean response time: 6.5 days
90th percentile: 20.2 days
Tracked items: 56

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 12% of issues opened in the past year have been closed. Three people close 95% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 13 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • clawsweeper:source-repro (10)
  • issue-rating: 🦞 diamond lobster (10)
  • clawsweeper:no-new-fix-pr (9)
  • P2 (8)
  • clawsweeper:fix-shape-clear (5)
  • clawsweeper:linked-pr-open (5)
  • impact:session-state (5)
  • clawsweeper:needs-maintainer-review (4)

Most active issues this week

Detailed Description

Lobster is an OpenClaw-native workflow shell designed to serve as a typed, local-first macro engine that transforms skills and tools into composable pipelines and safe automations. Built in TypeScript, it enables OpenClaw and other AI agents to invoke complex workflows in a single step, reducing token consumption and improving determinism and resumability compared to replanning every step. The project is classified across multiple domains including serverless computing, framework development, deployment tooling, function-as-a-service, multi-cloud support, extensibility, CLI tooling, application building, modularity, and lightweight architecture.

The core philosophy behind Lobster centers on several key design goals. It uses typed pipelines based on objects and arrays rather than text pipes, operates with local-first execution to avoid external dependencies, maintains a principle of not introducing new authentication surfaces by refusing to own OAuth tokens or credentials, and enables composable macros that agents can invoke in single steps to conserve computational resources. Workflow files are designed to read like small scripts, supporting deterministic shell and CLI steps via run or command directives, native Lobster pipeline stages, and approval gates that create hard workflow checkpoints between steps.

Lobster provides a command-line interface with several core commands. The exec command runs OS commands with optional stdin feeding in raw, JSON, or JSONL formats. Data shaping commands include where, pick, and head for filtering and transforming data. Rendering options provide json and table output formats. An approve command implements approval gates that function as TTY prompts or emit structured responses for OpenClaw integration. The graph command visualizes workflow structure before execution, supporting mermaid, dot, and ASCII output formats to show steps as nodes, data-flow edges from stdin references, conditional dependencies, and approval gates as diamond-shaped nodes.

Workflow files support multiple step types with shared argument, environment, and results models. Steps can reference prior step outputs via $step.stdout or $step.json for data passing without temporary files. Conditional execution is possible through when and condition directives. Steps support retry logic, timeout configuration in milliseconds, and on_error handlers for transient failure recovery. Approval steps can enforce identity constraints through required_approver, require_different_approver, and initiated_by fields, with environment variables LOBSTER_APPROVAL_INITIATED_BY and LOBSTER_APPROVAL_APPROVED_BY providing runtime identity information.

Lobster integrates with language models through native pipeline stages. The llm.invoke command calls models directly with provider resolution from command-line flags, environment variables, or auto-detection. Built-in providers include OpenClaw via OPENCLAW_URL and OPENCLAW_TOKEN, Pi via LOBSTER_PI_LLM_ADAPTER_URL, and HTTP via LOBSTER_LLM_ADAPTER_URL. The openclaw.agent command delegates to configured OpenClaw agents, handling agent identity, model defaults, sessions, and authentication. Workflow cost tracking uses static pricing tables with optional overrides via LOBSTER_LLM_PRICING_JSON for per-model pricing in USD per million tokens.

Development uses pnpm for package management, with TypeScript compilation to a dist directory before test execution. The roadmap includes shipping Lobster as an optional OpenClaw plugin tool to expand its integration capabilities.