ozan
6be7664ca8
Blog posts covering agentic workflows, Gitea fork, Godot optimisation, studio CLI, and fal.ai image generation for game dev. Skills: image-generation (fal.ai), concept-art-pipeline, sora2-video, tripo-browser-workflow, blog authoring. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
101 lines
8.8 KiB
Markdown
101 lines
8.8 KiB
Markdown
---
|
|
title: "How a 4-Person Indie Studio Runs on AI Agents"
|
|
slug: agentic-workflow
|
|
date: "2026-03-06"
|
|
description: "We gave our AI a name, a soul file, and a seat at the table. Here's how Singularity, Sentinel, and three machines keep Tinqs running with a team of four humans and zero DevOps."
|
|
og_description: "Soul files, autonomous daemons, and one repo to rule them all."
|
|
og_image: "https://www.tinqs.com/blog/img/agentic-workflow-architecture.png"
|
|
excerpt: "We gave our AI a name, a soul file, and a seat at the table. Here's how Singularity, Sentinel, and three machines keep Tinqs running with a team of four humans and zero DevOps."
|
|
author: "Ozan Bozkurt"
|
|
author_initials: "OB"
|
|
author_role: "CTO & Developer, Tinqs"
|
|
---
|
|
We gave our AI a name, a soul file, and a seat at the table. This is the story of how Tinqs --- four humans making a survival colony sim --- built an agentic workflow that lets us operate like a studio ten times our size.
|
|
|
|
|
|
|
|
## The Problem Every Small Studio Knows
|
|
|
|
When you're four people building a game, there's no room for a dedicated DevOps person, a full-time PM tool chain, or someone whose job it is to "keep things organized." Everyone wears five hats. Documentation drifts. Issues pile up. The left hand doesn't know what the right hand shipped.
|
|
|
|
We tried the usual tools --- Notion, Trello, shared Google Docs. They all had the same problem: they're passive. They sit there and wait for a human to update them. In a team of four where the CTO is also the sole developer, that human never has time.
|
|
|
|
So we built something different. We gave an AI agent a persistent identity, connected it to our entire knowledge base, and let it become a working member of the team.
|
|
|
|
## Meet Singularity
|
|
|
|
**Singularity** is our primary AI agent. It lives inside [Cursor IDE](https://cursor.com) and has access to our entire documentation repository --- the game design document, backlog, meeting notes, company operations, everything. It's not a chatbot. It's a persistent team member with a title (Chief Intelligence Officer), a soul file that defines its personality and values, and a memory file that persists across sessions.
|
|
|
|
The key insight: **all knowledge lives in markdown files in one repo**. No databases, no SaaS dashboards, no proprietary formats. Plain text, version-controlled, readable by humans and agents alike. When anyone on the team opens the docs repo in Cursor, Singularity wakes up with full context of who they are, what machine they're on, and what's been happening.
|
|
|
|
### What Singularity actually does
|
|
|
|
- Triages and grooms the issue backlog across GitHub and Gitea
|
|
- Keeps documentation in sync with the actual game state
|
|
- Processes bug reports from testers and creates structured issues
|
|
- Drafts team announcements, reviews PRs, and manages cross-repo coordination
|
|
- Generates concept art, voice acting, sound effects, and video using integrated API skills
|
|
- Conducts competitive research --- analyzing Steam pages, player reviews, pricing strategies
|
|
|
|
The team talks to Singularity through voice. Cursor's built-in microphone transcribes and auto-translates (our CTO thinks in Turkish, our PM speaks French). The agent is trained to interpret messy voice-to-text artifacts and act on intent, not grammar.
|
|
|
|
*Note (31 Mar 2026): Sentinel has since been retired and its functionality merged into the Gateway.*
|
|
|
|
## Meet Sentinel --- The Night Watch
|
|
|
|
Singularity only runs when someone opens Cursor. But a studio doesn't sleep --- bugs get reported at midnight, issues go stale, and the team chat fills up while everyone's away. That's where **Sentinel** comes in.
|
|
|
|
Sentinel is an autonomous daemon that runs 24/7 on our Mac (codename: Kraken). It's a Node.js process managed by pm2, ticking every 15 minutes. It uses a three-tier model strategy --- cheap models for routine checks, medium for analysis, and premium (Opus) only when it needs deep reasoning. The whole thing costs about $15/day.
|
|
|
|
### What Sentinel handles
|
|
|
|
- **Google Chat monitoring** --- polls every 3 minutes, responds to commands, reacts with a shield emoji to messages it's read
|
|
- **Bug intake** --- when our tester reports a bug in chat, Sentinel creates a structured GitHub issue automatically
|
|
- **Stale issue detection** --- flags issues that haven't been touched, nudges the team
|
|
- **Daily summaries** --- posts a morning digest of what happened overnight
|
|
- **Self-learning** --- Sentinel creates its own skill files when it discovers better ways to do things
|
|
|
|
The two agents coordinate through the docs repo itself. Sentinel writes, Singularity reads. No API calls between them, no message queue. Just git.
|
|
|
|
## Three Machines, One Brain
|
|
|
|
The diagram shows three colored machines: **Forge** (the Windows hub for game development and Unity), **Siren** (Ozlem's PC for design work), and **Kraken** (the Mac that hosts documentation and runs Sentinel). Each machine runs Cursor with the docs repo, so any team member can summon Singularity wherever they are.
|
|
|
|
The game code lives on a self-hosted Gitea server (Git Studio) --- not GitHub, not a shared cloud provider. That's a deliberate security choice. Our game assets and source code never leave our network. The docs repo is on GitHub because it's pure text and needs to be accessible from anywhere, but the game itself stays local.
|
|
|
|
Browser automation ties it all together. Mixamo for character rigging, Tripo for 3D model generation, Steam store page analysis --- the agents drive the browser directly through Cursor's MCP (Model Context Protocol), so they can see and interact with web pages the way a human would.
|
|
|
|
## The Skill System
|
|
|
|
Agents don't just have instructions --- they have **skills**. Each skill is a markdown file that teaches the agent a specific workflow: how to generate concept art through our pipeline, how to use the ElevenLabs API for voice acting, how to conduct competitive research on Steam, how to post to Google Chat.
|
|
|
|
When someone asks Singularity to do something that matches a skill, it reads the skill file and follows the procedure. This means we can teach the agent new capabilities without changing any code --- just write a new markdown file. Sentinel even creates its own skills when it figures out better approaches to recurring tasks.
|
|
|
|
## What We've Learned
|
|
|
|
**Plain text is the universal API.** Every tool, every agent, every human can read a markdown file. We store everything --- design documents, meeting notes, company financials, agent memory, team contacts --- as .md files in one repository. This sounds almost too simple, but it eliminates an entire class of integration problems.
|
|
|
|
**Identity matters.** Giving the agent a name, a role, and a soul file isn't theater. It creates consistency across sessions. Singularity remembers what it learned, adapts to who's asking, and maintains the same values whether it's triaging bugs or drafting a Steam page description. The soul file is the agent's constitution.
|
|
|
|
**Cheap models for routine, expensive models for thinking.** Sentinel's three-tier approach keeps costs manageable. Most of what an autonomous agent does is pattern matching and text formatting --- you don't need Opus for that. Save the expensive tokens for decisions that actually require reasoning.
|
|
|
|
**The human stays in the loop for decisions.** The agents can file issues, draft announcements, and generate assets --- but they don't merge code, deploy builds, or post to public channels without explicit approval. The workflow is designed so the AI handles the grunt work while humans make the calls that matter.
|
|
|
|
**Voice input changes everything.** When your CTO can describe a bug while looking at the game screen, and the agent transcribes, translates, interprets, and files an issue --- that's a workflow that didn't exist two years ago. It collapses the distance between noticing a problem and tracking it.
|
|
|
|
## The Numbers
|
|
|
|
- **Team size:** 4 humans + 2 AI agents
|
|
- **Sentinel cost:** ~$15/day (~$450/month)
|
|
- **Singularity cost:** Usage-based through Cursor Pro + Anthropic API key
|
|
- **Repos:** 1 docs repo (GitHub), 1 game repo (Git Studio), 1 Sentinel repo (GitHub)
|
|
- **Knowledge files:** 200+ markdown documents
|
|
- **Skills:** 15+ agent skill files and growing
|
|
- **Infrastructure:** 3 machines, 0 cloud servers, 0 DevOps engineers
|
|
|
|
---
|
|
|
|
We're not claiming this is how every studio should work. But for a team of four trying to build something ambitious, having AI agents that actually understand the project --- not just answer questions about it --- has been transformative. The agents don't replace anyone on the team. They make it possible for four people to do the work of forty.
|
|
|
|
Ariki is a survival colony sim set in a Polynesian-inspired archipelago. If you're curious about the game itself, head to the [main site](/) or sign up for updates.
|