Be concise for Paseo

A native companion to be-concise for Claude Code and Codex. Open Be concise in Paseo's sidebar, workspace panels, or Command Center. The composer badge shows enforcement status and decision counts. It opens a quick preview with a workspace enforcement toggle.

• Live hook decisions, searchable by tool, file, session, project, and reason. Pause the feed or open an event’s request and response.
• A composer badge with a monochrome icon, enforcement status, and decision counts; a compact popup with workspace stats and an enforcement switch. Turning enforcement off sets the workspace's softFail override; flagged actions are allowed while hooks and test-output filtering remain active. Turn it on to restore enforcement. Agent environment overrides apply separately.
• Call counts, interventions, sessions, average hook duration, and a 30-minute activity chart.
• User and project configuration with threshold controls, check switches, writing presets, an advanced JSON editor, and test filter settings.
• An isolated playground for file writes, Codex patches, shell commands, and final replies. Previews inspect hook responses without executing the pasted command or writing the target file.

Install

Requires Paseo 0.8.0 (including 0.8.0-beta.1) and be-concise 0.7.0 or newer on the daemon machine. The adapter uses the configuration, monitoring, and preview APIs shipped with be-concise 0.7.0. Paseo supplies all runtime dependencies.

paseo plugin add yannelli/paseo-plugin-concise
paseo plugin ls

For local development:

git clone https://github.com/yannelli/paseo-plugin-concise.git
cd paseo-plugin-concise
npm ci
npm run check
paseo plugin install "$PWD"
paseo plugin ls

Plugins must be enabled in Paseo Settings → Plugins. Installation runs trusted code with the daemon user’s access.

The plugin detects installed be-concise versions in the Claude and Codex caches, respecting CLAUDE_CONFIG_DIR and CODEX_HOME. For a source checkout or custom installation, set PASEO_CONCISE_ROOT in the daemon environment to the repository or plugins/concise directory, then reload this plugin.

Activity and settings

The view refreshes every two seconds. It follows the project registry and saved records under the daemon’s HOME/XDG directories, alongside any running concise-web console. It retains up to 500 events per project within a shared 16 MiB budget. Stats describe that retained window; they are not lifetime totals. New activity requires monitor.persist to be enabled and BEC_MONITOR_DISABLED to be unset in the agent’s environment.

Configuration controls edit the selected file and preserve its other keys. Save changes validates through be-concise and checks the file revision. An intervening edit preserves your draft and requires an explicit reload. The effective view uses the daemon’s environment; agent-specific environment overrides apply separately. The interface labels active and inactive layers because creating a higher-priority file changes which configuration is selected.

Each preview starts with separate retry state. Preview results do not enter live activity. The plugin does not modify the Claude or Codex installation or start another web console.

Development

npm run check
paseo plugin reload paseo-be-concise
paseo plugin logs paseo-be-concise

Tests use Node.js 24 and temporary home/project directories. They cover activity normalization, retention, stats, installation discovery, config conflicts, file permissions, and preview isolation. Integration tests require an installed be-concise; set PASEO_CONCISE_ROOT to a checkout to select it explicitly.

Paseo API reference: v0.8 plugins.

Releases

GitHub Actions runs the checks and publishes a GitHub release on qualifying pushes to main. The first release is v0.1.0. The workflow updates package.json and package-lock.json, pushes an annotated tag, and publishes release notes. It uses the repository's GITHUB_TOKEN; no extra secrets or npm publication are required.

Use Conventional Commits in commits and squash-merge titles:

The highest change since the last release determines the next version. For example, fix: repair the badge changes 0.1.0 to 0.1.1; feat: add a filter changes it to 0.2.0.

Run npm run release:dry-run from a clean main checkout with all tags fetched to preview the next release. Rerun the Release workflow to complete a publication interrupted after its tag was pushed.