“I'm a software developer. What can intouch do for me?”
One question, asked of a stock install. Nothing here is staged copy — this is the answer the assistant gave, played back.
Straight answer, developer to developer: InTouch replaces the cron-job-plus-scripts sprawl with a real orchestration layer that has logging, retries, alerting, and native AI baked in — running as a single JAR on a box you control (not a rented hosted runner).
• Keep GitHub Actions/Jenkins for the commit-to-merge loop — that's not what this is for.
• InTouch owns the scheduled, triggered, and operational work *around* the repo that CI never handled well: nightly jobs, deploys, log triage, monitoring.
• The inherited cron sprawl — nightly scripts scattered across boxes with no log, no retry, no owner. Each becomes a workflow: real logging, a result code, someone told when it fails. Usually the fastest first win.
• Release/deploy chores — git ops, SSH to target, rsync artifact, docker run, health check, rollback on bad exit code. Tasks chain output forward; a non-zero exit stops the chain unless you declare which codes count as success.
• Log triage — pull error lines, hand them to Claude/GPT/Gemini/local Ollama, get back one paragraph + severity instead of a 40MB file. Escalate only when it matters.
• Environment/dependency jobs — a runtime environment pins the interpreter, packages, and env vars so the script that works on your laptop works unattended at 3am.
• Anything with an API or a login — HTTP/REST (credentials handled outside your code, AES-256-encrypted vault, never exposed to the AI), plus S3, FTP/SFTP, SQL, MongoDB, Docker, shell.
• Write your own tool if nothing installed covers it — either a declarative IML tool (no compile) or a JAR implementing IToolConnector. Once registered it's a peer to every other tool, usable in workflows and by the assistant, with its own credential type.
Want me to build one of these for real right now — say, wrap a specific script you've got into a scheduled workflow with failure alerting, or set up log triage against an actual log file? Tell me what's currently cron'd or manual and I'll turn it into a workflow.
It answered like this because it knew who was asking.
The same assistant answers a shop owner about supplier price files and a sysadmin about cron sprawl. Same engine, same tools, same audit trail — sharpened to the person asking.