Theoses
AI assistant & coding agent
A self-hosted personal assistant and coding agent, built on the pi coding agent and forked to suit my own workflow.
Runs my scheduled work every day: purchasing alerts, reports and content.
Drag sideways to turn it.
Try it
A small working version of the workflow, running in your browser with fictional data.
Task: draft this week’s stock report
Sample dataTheoses does the groundwork, then stops for your review. This is a staged demo; nothing is sent.
- Read the inventory export
- Compare with last week
- Draft the report
Draft for review
Gauze swabs dropped below the reorder point on Tuesday. Two purchase orders are ready for Tanjung Clinical and Meridian Medical. Glove use is up on last week.
The problem
Research, files, reports and code changes need continuity across conversations, and important actions still need human review.
What I built
Theoses started as a fork of Mario Zechner’s pi coding agent, which I reshaped around how I work. It reads and edits files, runs commands, researches questions and uses extensions in real projects. Persisted sessions, working notes and durable memory carry context between tasks.
How it works
- Ask about a real workspace
- Inspect files and evidence
- Prepare a draft or change
- Review before consequential action
Under the hood
A Node.js and TypeScript runtime powers the terminal, Telegram and dashboard channels. Its tool loop can be extended with skills, providers and integrations. Channel sessions and durable memory serve different roles.
What this page does not claim
The images are staged sample conversations in the genuine dashboard, not live AI execution. The portfolio sends no messages, creates no orders and changes no files. The agent itself is not a filesystem or network sandbox.
What should your software do?
Tell me what your team does today, what gets repeated, and what a better workflow would look like.

