Cyber Shell

cyber-shell is a local CLI wrapper for interactive Bash on Linux/Kali. It runs a real shell inside a PTY, preserves normal terminal behavior, captures command/output/exit code/cwd, and sends telemetry to a configurable HTTP endpoint in fail-open mode.

On Windows, use cyber-shell ask from PowerShell for chat and Burp MCP interaction. The PTY shell wrapper mode is Linux/POSIX-only.

endpoint_url is the URL of the receiving server. For local testing, that can be the same machine running the mock endpoint. For real deployment, it should point to your backend or AI ingestion server, not to the student machine unless that machine is intentionally hosting the receiver.

Features

• Runs a real interactive Bash session inside a PTY.
• Relays stdin/stdout in raw terminal mode with resize support.
• Uses shell hooks over a dedicated control pipe instead of printing markers into the terminal.
• Captures one logical event per command with:
  • cmd
  • output
  • exit_code
  • cwd
  • started_at
  • finished_at
  • is_interactive
• Sends telemetry asynchronously with timeout, retry, and fail-open behavior.
• Truncates oversized command output with max_output_bytes.
• Includes a built-in mock endpoint and dashboard for local testing.
• Strips ANSI color/control sequences from telemetry output while keeping the local terminal unchanged.

Install

Assume Python 3 and pip are already installed and working normally.

python3 -m pip install cyber-shell-wrapper

Quick Start

The fastest test flow uses two terminals.

Terminal 1: start the mock endpoint

cyber-shell mock-endpoint --host 0.0.0.0 --port 8080 --api-key replace-me

Open the dashboard locally:

http://127.0.0.1:8080/

If you are accessing it from another machine:

http://<server-ip>:8080/

Check that the endpoint is alive:

curl -i http://127.0.0.1:8080/health

Terminal 2: start the wrapped shell and point it at the mock endpoint

cyber-shell --endpoint-url http://127.0.0.1:8080/api/terminal-events --api-key replace-me

Alternative: export the variables first, then start cyber-shell

export CYBER_SHELL_ENDPOINT_URL=http://127.0.0.1:8080/api/terminal-events
export CYBER_SHELL_API_KEY=replace-me
cyber-shell

Inside that wrapped shell, run a few commands:

whoami
pwd
ls -la

To confirm that you are inside the wrapped session:

echo $CYBER_SHELL_SESSION_ID

If it prints a value like sess-..., you are inside a cyber-shell session.

Windows

Use PowerShell as the primary shell on Windows.

cyber-shell ask works on Windows without terminal capture. This mode is intended for chat plus local Burp MCP interaction only.

Example:

cyber-shell ask "search Burp history for login"

cyber-shell start is not supported on Windows because the PTY wrapper depends on POSIX APIs.

Configuration

By default, cyber-shell reads:

~/.config/cyber-shell/config.yaml

The config format is intentionally simple YAML with optional environment variable overrides.

Runtime precedence is:

• CLI arguments
• environment variables
• config file
• built-in defaults

When you start the wrapped shell with runtime overrides such as --endpoint-url, --api-key, or exported CYBER_SHELL_* variables, cyber-shell writes the effective values back into ~/.config/cyber-shell/config.yaml. In this project, that file acts as a temporary session cache so later terminals can reuse the same lab settings without retyping them.

Sample config:

endpoint_url: "http://127.0.0.1:8080/api/terminal-events"
api_key: "replace-me"
timeout_ms: 3000
retry_max: 3
retry_backoff_ms: 1000
max_output_bytes: 262144
queue_size: 256
shell_path: "/bin/bash"
metadata:
  hostname_group: "kali-lab"

Print the default template:

cyber-shell print-default-config

Supported environment overrides:

• CYBER_SHELL_CONFIG
• CYBER_SHELL_ENDPOINT_URL
• CYBER_SHELL_API_KEY
• CYBER_SHELL_BURP_MCP_URL
• CYBER_SHELL_TIMEOUT_MS
• CYBER_SHELL_RETRY_MAX
• CYBER_SHELL_RETRY_BACKOFF_MS
• CYBER_SHELL_MAX_OUTPUT_BYTES
• CYBER_SHELL_QUEUE_SIZE
• CYBER_SHELL_SHELL_PATH

Telemetry Flow

The wrapper sends telemetry with POST requests to endpoint_url.

• Local test flow:
  • cyber-shell posts JSON to http://127.0.0.1:8080/api/terminal-events
  • the mock endpoint displays those events in its dashboard
• Production flow:
  • cyber-shell posts JSON to your backend or AI ingestion server
  • that server stores the events, forwards them, or exposes them to downstream AI components

The wrapper does not need to GET logs back from the AI server for the core design. The primary contract is outbound POST from the PTY wrapper to the server. Optional GET endpoints such as GET /events are only for debugging, review, or dashboards.

Manual Endpoint Test

You can test the dashboard without starting the wrapped shell:

curl -i -X POST http://127.0.0.1:8080/api/terminal-events \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer replace-me" \
  -d '{"session_id":"s1","seq":1,"cmd":"whoami","cwd":"/home/kali","exit_code":0,"output":"kali","output_truncated":false,"started_at":"2026-03-21T10:00:00Z","finished_at":"2026-03-21T10:00:01Z","is_interactive":false,"hostname":"kali","shell":"bash","metadata":{}}'

Notes

• This tool targets POSIX/Linux, with Kali as the primary environment.
• V1 does not semantically parse vim, top, nano, less, or man; it only preserves terminal behavior and finalizes the event when the prompt returns.
• Nested shells and remote shells are treated as opaque terminal streams.
• The wrapper does not capture raw keystrokes for the entire session.

Dev Checks

python -m unittest discover -s tests -v
python -m compileall src tests