Open Source & Community

Contributing to Last Signal

Development workflow, codebase architecture, and an open invitation for TypeScript developers to help build the TypeScript module.

Last updated: 2026-10-31•v0.1.0

Last Signal is a community-driven open-source project licensed under MIT. We believe that transparent, evidence-grounded agent debugging must be open to every developer, across every programming language and runtime.

Help Build the TypeScript Module

LOOKING FOR CONTRIBUTORS // TYPESCRIPT MODULE

Last Signal is open source, and its next chapter needs more hands. The Python CLI establishes the forensic foundation. Now, we're looking for TypeScript developers interested in helping build its TypeScript module and bring evidence-grounded agent forensics to the JavaScript ecosystem.

Help Build the TypeScript Module → GitHub Repository

With the rapid rise of TypeScript-based agent frameworks (such as LangChain.js, Vercel AI SDK, Mastra, and custom Node.js/Bun agents), there is an urgent need for native TypeScript agent supervision and trace reconstruction.

We invite developers from the TypeScript and JavaScript ecosystem to participate in:

Architecture & API Design: Designing a native, non-blocking process supervisor and telemetry stream collector for Node.js, Bun, and Deno.
Rule Porting: Implementing the deterministic state-machine rules (RULE-REPEATED-TOOL-FAILURE, RULE-UNPRODUCTIVE-RETRY-LOOP, etc.) with typed schemas.
Framework Adapters: Building zero-overhead middleware for popular TS agent frameworks.
Tests & Documentation: Crafting high-coverage test suites and developer documentation.

Explore the existing Python implementation in the repository to understand the forensic detection philosophy and architecture, then join the discussions on GitHub!

Development Setup & Workflow

To contribute to the Python implementation, fork and clone the repository:

bash

$git clone https://github.com/sahilsalunke42/last-signal.git

$cd last-signal

$# Create a virtual environment and activate it

$python -m venv venv

$source venv/bin/activate # On Windows: venv\Scripts\activate

$# Install editable development dependencies

$pip install -e ".[test]"

Testing & Code Quality Standards

Run the comprehensive test suite with pytest before submitting pull requests:

bash

$pytest tests/ -v

========================== test session starts ==========================

collected 14 items

tests/test_detector.py::test_repeated_tool_failure PASSED

tests/test_detector.py::test_unproductive_retry_loop PASSED

tests/test_detector.py::test_terminal_tool_failure PASSED

tests/test_detector.py::test_unrecovered_execution_failure PASSED

tests/test_runner.py::test_supervisor_stream_capture PASSED

tests/test_report.py::test_markdown_postmortem_generation PASSED

========================== 14 passed in 0.82s ===========================

Pull Request & Review Process

1. Open an issue on GitHub to discuss proposed architecture changes or new failure rules.
2. Create a feature branch: git checkout -b feat/my-contribution.
3. Ensure all pytest tests pass and code adheres to PEP 8 standards.
4. Submit a Pull Request referencing your discussion issue.

GitHub Repository

All development, discussions, issues, and pull requests are managed at https://github.com/sahilsalunke42/last-signal.

Help Build the TypeScript Module

LOOKING FOR CONTRIBUTORS // TYPESCRIPT MODULE

Help Build the TypeScript Module → GitHub Repository

We invite developers from the TypeScript and JavaScript ecosystem to participate in:

Architecture & API Design: Designing a native, non-blocking process supervisor and telemetry stream collector for Node.js, Bun, and Deno.

Rule Porting: Implementing the deterministic state-machine rules (RULE-REPEATED-TOOL-FAILURE, RULE-UNPRODUCTIVE-RETRY-LOOP, etc.) with typed schemas.

Framework Adapters: Building zero-overhead middleware for popular TS agent frameworks.

Tests & Documentation: Crafting high-coverage test suites and developer documentation.

Explore the existing Python implementation in the repository to understand the forensic detection philosophy and architecture, then join the discussions on GitHub!

Development Setup & Workflow

To contribute to the Python implementation, fork and clone the repository:

bash

$git clone https://github.com/sahilsalunke42/last-signal.git

$cd last-signal

$# Create a virtual environment and activate it

$python -m venv venv

$source venv/bin/activate # On Windows: venv\Scripts\activate

$# Install editable development dependencies

$pip install -e ".[test]"

Testing & Code Quality Standards

Run the comprehensive test suite with pytest before submitting pull requests:

bash

$pytest tests/ -v

========================== test session starts ==========================

collected 14 items

tests/test_detector.py::test_repeated_tool_failure PASSED

tests/test_detector.py::test_unproductive_retry_loop PASSED

tests/test_detector.py::test_terminal_tool_failure PASSED

tests/test_detector.py::test_unrecovered_execution_failure PASSED

tests/test_runner.py::test_supervisor_stream_capture PASSED

tests/test_report.py::test_markdown_postmortem_generation PASSED

========================== 14 passed in 0.82s ===========================

Pull Request & Review Process

1. Open an issue on GitHub to discuss proposed architecture changes or new failure rules.

2. Create a feature branch: git checkout -b feat/my-contribution.

3. Ensure all pytest tests pass and code adheres to PEP 8 standards.

4. Submit a Pull Request referencing your discussion issue.

GitHub Repository

All development, discussions, issues, and pull requests are managed at https://github.com/sahilsalunke42/last-signal.