AI AGENT · OPENCLAW

The project log,
one message away.

An AI agent I run on Telegram for project tracking: it logs progress as it happens, answers about deliverables, milestones, meetings and documentation by querying a knowledge base, and prepares the status reports.

OpenClawTelegramDockerGemma · llama.cppGitObsidianGoogle Calendarn8n (MCP)

WHAT IT IS FOR

Log. Ask.
Report.

The status of a project usually lives scattered across emails, minutes and the memory of whoever manages it. Here what happens each day is recorded and forms a timeline of the project, milestones and deliverables live in a log, and the calendar brings in the meetings. With that, the agent answers in seconds how the project is going, what is coming due, what is blocked and where each document is.

04Specialized agents

03Models: cloud and on-premise

01Channel and a single owner

HOW IT IS USED

One conversation, three tasks.

Jupiteragent · online

Log progress: we finished the technical review of the equipment purchase process. The finance team’s comments are still pending.

Logged ✓ ACT-2026-01-12-003
Jan 12 · 22:39 (America/Bogota)
“The technical review of the equipment purchase process was completed; the finance team’s comments are still pending.”
I linked it to deliverable E3 · Technical study and saved your original text next to the drafted version.

How is the project going?

From the project log and your calendar:
• Milestones: 4 of 7 reached. Next is “Supplier award”, on January 30.
• Deliverables in progress: E3 · Technical study (due Fri 16) and E4 · Risk matrix (no date).
• Blocking item: the finance team’s comments on E3.
• Meetings: follow-up committee, Thursday 15 at 10:00.

Prepare the summary for Thursday’s committee.

Done. I gathered the progress since the last committee, the deliverables coming due and the pending decisions in borradores/comite-2026-01-15.md. It is already in your Obsidian vault; the changes go up to Git tonight.

HOW IT IS BUILT

Several small agents,
each with just enough.

CONVERSATION

Jupiter

The one that talks to you on Telegram: it logs progress, answers about milestones, deliverables and meetings, and asks the other agents for help.

✓ Telegram✓ Cloud model✓ Coordinates agents

KNOWLEDGE BASE

Knowledge

It searches the project log and documentation. It runs in an isolated container and can only read.

✓ Read only✕ No network✕ No execution✕ No writing

DRAFTS

Drafts

It writes status reports, meeting summaries and documents in Markdown. It can only write to the drafts folder.

✓ Writes drafts✕ No network✕ No execution✕ No browser

LOCAL MODEL

Mimas

It uses a Gemma model hosted on-premise. It can run commands, but each one waits for my approval.

✓ On-premise model✓ Runs with approval

THE MEMORY

Files you
can read.

The agent records what happens each day in JSONL files, one per month. Those records form the project timeline: they are used to track it and to look up later what happened, when and in what order. The plan of milestones and deliverables, agent memory and reports are text files too. System scheduled tasks take care of backups and push the changes to Git, and the folder syncs with Obsidian.

workspaces/jupiter/
├─ proyectos/proyecto-demo/
│  ├─ hitos-y-entregables.json         ← plan: milestones, deliverables, dates
│  ├─ configuracion.md
│  ├─ registros/2026/
│  │  ├─ 2026-01.jsonl                 ← one file per month
│  │  └─ 2026-02.jsonl                 ← what happens each day
│  ├─ borradores/                      ← status reports and summaries
│  └─ respaldos/
└─ backups/agents-md/                  ← agent memory

{"id":"ACT-2026-01-12-003","version":1,
 "fecha":"2026-01-12","hora":"22:39:58","zona_horaria":"America/Bogota",
 "texto_original":"Log progress: we finished the technical review…",
 "actividad_realizada":"The technical review of the equipment purchase process was completed…"}

DESIGN DECISIONS

Each agent, with the least privilege

Instead of one assistant that can do everything, there are several with narrow jobs. The one that queries the knowledge base only reads; the one that drafts only writes to its folder. Both run in Docker containers with no network, a read-only file system and no privileges, so a mistake or a malicious instruction inside a document cannot go any further.

A single owner, a single channel

The agent only answers my Telegram user. Its service listens only on the machine itself, with authentication, and is not exposed to the internet. Device actions it does not need (camera, screen recording, messages, contacts) are blocked, and system commands wait for my approval.

Plain-text, versioned memory

Nothing lives in an opaque database. Memory is Markdown files and the project’s day-to-day is stored as JSONL, one file per month, keeping my original text next to the drafted version: a timeline that can be walked through and queried. A scheduled task pushes the changes to Git: everything is readable, auditable and portable to another tool.

Available wherever I am

The reports and documents it produces sync with my Obsidian vault, so I can read and edit them from my computer or phone. Asking or logging something takes one Telegram message: tracking happens in the moment, not the night before the committee.

THE NEXT STEP

Good ideas deserve
a good plan.

Let's talk about yours