convez.ai
AgenteDevOps & InfraestruturaIntermediário
kt0319

any-console

kt0319/any-console

Console dev web compartilhado entre celular e PC com tmux persistente

Ver no GitHub
InicialPluginScore · de 0 a 100

Console web para acessar sessões tmux, operações Git e terminal do navegador em qualquer dispositivo. Sincroniza tarefas de shell, commits e execução de scripts entre PC e celular mantendo as sessões persistentes.

Instalação

$npx convez-ai kt0319/any-console

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 1 dia
Versão
v0.21.0
Issues abertas
1
Contribuidores
6

Casos de uso

  • Acessar seu terminal de trabalho do celular durante deslocamentos
  • Executar testes, commits e deploys de forma integrada via web
  • Manter sessões tmux ativas independente do dispositivo usado

Veredito

Ferramenta robusta e bem-arquitetada para fluxos de desenvolvimento distribuídos, com foco genuíno em UX mobile e automação. Requer Linux como host, mas clientes funcionam em qualquer navegador moderno — excelente para equipes que precisam de produtividade em movimento.

README

A tradução para o português deste README ainda está na fila.

any-console

Release Last commit CI codecov License: MIT Python 3.11+ Vue 3 FastAPI

A seamless dev console across phone and PC. A self-hosted web environment where the same tmux session is accessible from any device via a browser.

Website: https://any-console.highedge.net/

Why any-console?

  • Seamless across devices — Start npm test on your PC, check the output on your phone during commute, and pick up where you left off when you get home. tmux sessions persist — closing the browser doesn't end the session.
  • Serious mobile input — A custom virtual keyboard with flick input. Practical enough to run git commit from your phone.
  • Jobs, Git, and terminal in one place — No tab-switching between tools. Run scripts, commit, and push — all in one tap.

Features

  • Persistent sessions — tmux × WebSocket; switch devices without losing your session
  • Mobile-optimized input — Custom flick keyboard with swipe support
  • Web terminal — xterm.js based, multi-tab and split-pane
  • Git UI — Branch switching, commit, push/pull, diff, history, stash, merge/rebase
  • Job runner — One-tap shell script execution; define and edit jobs from the UI
  • PWA — Installable on phone and desktop
  • Lightweight stack — Vue 3 + Pinia + FastAPI, built with Vite

Platform support

Client side: any OS, any device with a modern browser. This is the whole point of any-console — open https://<your-host>/ from your phone, laptop, or any browser and you get the full UI.

Host (server) side: Linux only for real use. The runtime is POSIX-portable, but the operational pieces that make any-console useful (systemd for service management, tmux for persistent sessions, the ./any-console helper) all assume Linux.

Host setupPlatformsStatus
systemd (first-class)LinuxSupported. Daily-use target.
DockerLinux / macOS / WindowsDemo / sandbox only — not suitable for real workspaces.

The host running any-console needs Linux. Browser access from macOS / Windows / iOS / Android is fully supported and is the intended client experience. Docker exists to let curious users try the UI without provisioning a Linux box; the host's workspaces, SSH keys, git/gh config, and shell environment are intentionally not threaded into the container.

Setup

Which one should I use?

  • You have a Linux host and want to actually use any-console → ./any-console setup (systemd). Your SSH keys, git/gh config, and shell environment all carry over; tmux sessions persist across reboots.
  • You just want to try the UI from any OS → Docker. Runs in seconds on macOS / Windows / Linux, but the container has no access to your real workspaces, keys, or shell — only the bundled ./work directory.

systemd (Linux) — first-class

git clone https://github.com/kt0319/any-console.git
cd any-console
./any-console setup

Installs dependencies, builds the frontend, and registers a systemd service in one step. After this, manage the service with ./any-console start|stop|update|logs|... (see Commands).

Docker (Linux / macOS / Windows) — demo / sandbox

git clone https://github.com/kt0319/any-console.git
cd any-console
docker compose -f docker/compose.yml up -d

Open http://<host>:8888.

The default compose file mounts only ./work inside the repository as the workspace root. The container has its own user, no host SSH keys, no host git/gh config, and no access to the host shell environment. That makes Docker fine for trying any-console out, but ill-suited for daily work on your real projects.

The ./any-console CLI does not manage Docker containers. Use docker compose directly for start/stop/logs, and git pull && docker compose ... up -d --build to update.

Requirements

Required:

  • Python 3.11+
  • Node.js 18+
  • git — used by the Git UI
  • tmux — required for terminal session management

Optional:

  • gh (GitHub CLI) — for fetching GitHub repos, issues, PRs, and Actions

Installation examples:

# Debian/Ubuntu
sudo apt install python3 nodejs git tmux
# optional: follow the official gh install guide

# macOS
brew install python node git tmux gh

Authentication

  • On first start, if data/auth.json does not exist, a random 32-character token is generated and saved automatically.
  • The connection URL is printed to stdout and journalctl once. Open it on your device to start an authenticated session.
  • On subsequent starts, data/auth.json is never overwritten.
  • The token can be changed from the "Security" settings in the UI.

Disabling authentication (for closed networks like Tailscale)

# via environment variable
ANY_CONSOLE_DISABLE_AUTH=1 ./any-console start

# or in config.json
# "auth_disabled": true

HTTPS

PWA installation and service workers require HTTPS.

Tailscale Serve is the easiest option — it handles certificates automatically:

tailscale serve --bg / proxy http://127.0.0.1:8888

Access the app at https://<your-device>.ts.net/.

Direct TLS is also supported via environment variables:

SSL_KEYFILE=/path/to/key.pem SSL_CERTFILE=/path/to/cert.pem ./any-console start

The default port is 8888. To change it, set __global__.port in config.json.

Commands

For the systemd setup, all operations go through the ./any-console command. (Docker users: manage with docker compose instead — see Platform support.)

./any-console setup      First-time setup (install deps + build + register systemd)
./any-console update     Update to latest (git pull + update deps + build + restart)
./any-console start      Start the service          (systemctl start)
./any-console stop       Stop the service           (systemctl stop)
./any-console restart    Restart the service        (systemctl restart)
./any-console status     Show status (service state, URL, version)
./any-console logs       Show service logs          (journalctl)
./any-console run        Run in foreground (no systemd; macOS / WSL / etc.)
./any-console version    Show version

run skips systemd entirely and starts the API directly via python3 -m api.main. Useful for macOS / WSL or for quick test runs on a Linux box without registering a service.

Updating

./any-console update

Runs git pull → update deps → build → restart in one shot. Skips steps where nothing has changed.

Repository layout

api/      Backend (FastAPI)
ui/       Frontend (Vue 3 + Pinia, built with Vite)
docker/   Docker files
docs/     Architecture & design docs

See docs/ARCHITECTURE.md for the module-level breakdown.

Configuration

  • Workspace settings (icons, job definitions, links, etc.) are stored in config.json.
  • Generated automatically on first run. To configure manually, copy config.json.example and edit it.
  • Export/import is available from the settings modal.

Project Stance

any-console started as a tool built for daily real-world use, and it stays close to that origin: pragmatic, opinionated, and focused on what actually gets used.

  • Issues and PRs are welcome. Responses may take a while, but they are read.
  • The project has a clear design philosophy (see CLAUDE.md). Contributions that fit that direction are the easiest to land; ones that pull elsewhere may work better as a fork — that is the spirit of MIT.
  • Releases come when they're ready. A quiet month does not mean the project is abandoned.
  • The roadmap is lightweight. Features land as they prove useful in practice.

If that sounds good to you, welcome aboard.

License

MIT

Ver o original no GitHub

Bom para

Relacionados