sidecar

Sidecar runs alongside CLI agents to provide real-time visibility into workflow execution through a terminal-based interface. It displays diffs, file trees, conversation history, and task management capabilities, reducing context switching during development and operations work. The tool integrates with Claude and other AI agents, offering keyboard-driven navigation including vim-style bindings and pane resizing controls. Developers and operations teams use Sidecar to streamline agent-assisted workflows by consolidating multiple tools into a single, cohesive terminal environment. Key features include configurable plugins (file-browser, git-status, conversations, workspace), persistent state management, and the ability to disable plugins as needed.

[{"step":"Configure Sidecar for your repository","action":"Run `sidecar init --config [PATH_TO_CONFIG]` to set up the sales pipeline automation. Replace [PATH_TO_CONFIG] with the path to your Sidecar configuration file (e.g., `./sales-pipeline/.sidecar/config.yml`).","tip":"Use the provided diff template to define triggers for Sortd events (e.g., new email, task completion) and map them to pipeline actions."},{"step":"Integrate Sortd with Sidecar","action":"Set up Sortd webhooks to send Gmail events to Sidecar. In Sortd, navigate to 'Settings > Webhooks' and add an endpoint pointing to your Sidecar server (e.g., `https://your-server.com/sortd-webhook`).","tip":"Test the webhook integration by sending a test email to your shared inbox (e.g., `[email protected]`). Verify the event appears in Sidecar's conversation history."},{"step":"Generate and review the diff","action":"Use `sidecar diff` to visualize changes made to your repository after integrating Sortd. Pay attention to the `.sidecar/boards/` directory, which will contain Kanban-style boards synced from Sortd.","tip":"Compare the diff against your team's workflow documentation to ensure all steps are accounted for. Use `sidecar tree` to inspect the file structure."},{"step":"Train your team on Sidecar commands","action":"Schedule a 15-minute training session to teach your team how to query Sidecar for pipeline status. Key commands: `sidecar status --lead [LEAD_NAME]`, `sidecar history --lead [LEAD_NAME]`, and `sidecar logs`.","tip":"Create a cheat sheet with common Sidecar queries and share it in your team's Slack channel or internal wiki."},{"step":"Monitor and iterate","action":"Use Sidecar's `sidecar logs` to track pipeline performance. Identify bottlenecks (e.g., delays in updating lead status) and refine your Sidecar configuration accordingly.","tip":"Set up Sidecar to send alerts to your team's Slack channel when critical pipeline events occur (e.g., 'Quote Requested' status)."}]