tinqs/blog
5
0
Fork 0
Code Pull Requests Actions Packages Projects Releases Wiki Activity Issues

blog: refresh posts to current infra state (JS flows, tinqs CLI, steering + human-in-the-loop)

Browse Source
This commit is contained in:
ozan
2026-06-10 21:47:13 +01:00
parent aaa788b29f
commit 6cba781083
6 changed files with 83 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files
posts/studio-cli.md
+5 -5
View File
@@ -12,11 +12,11 @@ author_role: "CTO & Developer, Tinqs"
---
Every AI agent session starts the same way: cold. The agent doesn't know what project this is, who's asking, what tools are available, or what happened yesterday. You spend the first five minutes re-explaining context.
Our CLI solves this in 100ms. One command — `tstudio identity` — and the agent knows everything. The binary is 15MB, has zero runtime dependencies, and runs on every machine in the studio.
Our CLI solves this in 100ms. One command — `tinqs identity` — and the agent knows everything. The binary is 15MB, has zero runtime dependencies, and runs on every machine in the studio.
## The identity command (100ms)
When an agent starts, the first thing it calls is `tstudio identity`. The output:
When an agent starts, the first thing it calls is `tinqs identity`. The output:
- **Soul file** — the agent's persistent identity, values, operating principles
- **Company context** — team members, roles, what the company does
@@ -26,7 +26,7 @@ When an agent starts, the first thing it calls is `tstudio identity`. The output
This data lives in markdown files in the docs repo. Any machine on the network can read it. The agent goes from blank to fully contextual in under a second.
This started as a convenience tool for humans. It became the single most important function in our stack. Every agent session — Cursor, Claude Code, Pi — starts with `tstudio identity`. Without it, every conversation begins with "let me explain the project." With it, the agent already knows.
This started as a convenience tool for humans. It became the single most important function in our stack. Every agent session — Cursor, Claude Code, Pi — starts with `tinqs identity`. Without it, every conversation begins with "let me explain the project." With it, the agent already knows.
## Screenshots and cloud vision
@@ -38,7 +38,7 @@ This is how you file bugs without typing. Look at the game, tell the agent what'
## Health checks
`tstudio doctor` runs a comprehensive check:
`tinqs doctor` runs a comprehensive check:
- Is the git platform reachable and authenticated?
- Is the game server running?
@@ -55,7 +55,7 @@ Cross-compilation is trivial. We build Windows, Mac (arm64 + amd64), and Linux b
## What we learned
**The CLI is the API for AI agents.** What started as a human convenience tool became the primary interface for agents. Every session starts with `tstudio identity`. The agent's "hands and eyes" — screenshots, vision, health checks — are subcommands of the same binary.
**The CLI is the API for AI agents.** What started as a human convenience tool became the primary interface for agents. Every session starts with `tinqs identity`. The agent's "hands and eyes" — screenshots, vision, health checks — are subcommands of the same binary.
**One binary beats ten scripts.** Scripts rot. They have different shells, different PATH assumptions, different error handling. A compiled binary either works or it doesn't. It ships with dependencies baked in. It doesn't care if your Python is 3.9 or 3.12.