Public docs

Logtura Docs

How the hosted control panel, open-source forwarder, and deployment model fit together.

GitHub

Use Logtura with Claude Code or Codex

The Logtura skill helps your coding agent connect project logs, configure sources and destinations, and update an existing forwarder. It includes Cloudflare, Fly.io, Railway, Vercel, and Supabase recipes.

Standalone use needs no Logtura account. Install Node.js 22+ and the @logtura/cli package (0.3.6 or later) as well as the skill. Provider credentials are needed for live discovery and delivery.

Quick install from skills.sh

Install the portable skill into a supported local agent from the public skills.sh listing:

npx skills add logtura/logtura --skill logtura

Use the native marketplace instructions below when you prefer client-managed plugin updates or want to pin an immutable release checkout.

Install Git LFS and run git lfs install once before cloning a marketplace. Release archives include image bytes directly and do not require Git LFS. Claude Code 2.1.291 skips LFS hydration when it clones a GitHub marketplace; use the hydrated checkout below so its installed icon contains actual PNG bytes.

Claude Code

git clone https://github.com/logtura/logtura.git "$HOME/.local/share/logtura-agent-skills"
claude plugin marketplace add "$HOME/.local/share/logtura-agent-skills"
claude plugin install logtura@logtura --scope user

In a new session, invoke /logtura:logtura and describe the project, sources, and destination. For example: “Set up standalone Logtura forwarding for this Worker's errors and verify a test event reaches my webhook.”

Codex

codex plugin marketplace add logtura/logtura
codex plugin add logtura@logtura

Select logtura:logtura in the skill picker or invoke $logtura:logtura with your task. For an existing deployment: “Pull my website deployment, add this new site, push the update, and verify the website and forwarder agree.”

Update an existing forwarder

The skill uses the CLI's pull/edit/push workflow and preserves deployment IDs. It checks both the accepted website configuration and the forwarder's applied configuration, then verifies actual event delivery.

Source host support and forwarder deployment targets are separate. The CLI has a native Fly deploy path; generated Docker bundles can run on another Docker host. The skill does not add native Railway or Vercel forwarder deploy commands.

These instructions target local coding clients with shell access. Installing a skill does not grant credentials or synchronize local tools to a cloud session.

See the complete installation guide for update/removal commands, version pinning, standalone skill-folder installation, and tested client versions. The GitHub marketplaces are the owned distribution source; vendor-directory approval is a separate step.