Pi Agent — Tinqs Studio Fork

Tinqs Studio's fork of Pi (earendil-works/pi), configured for autonomous game and platform development with DeepSeek V4 as the primary LLM. Lives at tinqs.com/tinqs/pi.

---

Tinqs Configuration

Custom extensions in .pi/extensions/:

• tinqs-provider.ts — Registers DeepSeek V4 Flash and Pro models routed through the Tinqs Studio API proxy (https://tinqs.com/api/v1/ai). Auth via TINQS_AGENT_TOKEN env var (Gitea PAT). Uses the openai-completions API with DeepSeek-native thinking format.
• tinqs-tools.ts — Three custom tools:
  • gitea_api — Call the Gitea REST API for repo operations, PRs, and issues.
  • fal_generate — Generate images via fal.ai (flux-2-pro). Auth via FAL_KEY.
  • nova_describe — Describe images via Amazon Nova Lite (Bedrock). Auth via AWS credentials.

Skills in .pi/skills/:

• tinqs-studio.md — Platform conventions (git, languages, testing, security).
• ariki-game.md — Ariki game development (Godot 4.6, C#, build/test commands, asset pipeline).

Environment variables:

Variable	Purpose
TINQS_AGENT_TOKEN	Gitea PAT — used for both LLM proxy auth and Gitea API calls
FAL_KEY	fal.ai API key for image generation
AWS_ACCESS_KEY_ID	AWS credentials for Nova Lite image understanding
AWS_SECRET_ACCESS_KEY	AWS credentials for Nova Lite image understanding
AWS_REGION	AWS region (defaults to eu-west-1)
TINQS_URL	Tinqs Studio base URL (defaults to https://tinqs.com)

---

Upstream Pi

• @earendil-works/pi-coding-agent: Interactive coding agent CLI
• @earendil-works/pi-agent-core: Agent runtime with tool calling and state management
• @earendil-works/pi-ai: Unified multi-provider LLM API (OpenAI, Anthropic, Google, …)

To learn more about pi:

• Visit pi.dev, the project website with demos
• Read the documentation, but you can also ask the agent to explain itself

Share your OSS coding agent sessions

If you use pi or other coding agents for open source work, please share your sessions.

Public OSS session data helps improve coding agents with real-world tasks, tool use, failures, and fixes instead of toy benchmarks.

For the full explanation, see this post on X.

To publish sessions, use badlogic/pi-share-hf. Read its README.md for setup instructions. All you need is a Hugging Face account, the Hugging Face CLI, and pi-share-hf.

You can also watch this video, where I show how I publish my pi-mono sessions.

I regularly publish my own pi-mono work sessions here:

• badlogicgames/pi-mono on Hugging Face

All Packages

Package	Description
@earendil-works/pi-ai	Unified multi-provider LLM API (OpenAI, Anthropic, Google, etc.)
@earendil-works/pi-agent-core	Agent runtime with tool calling and state management
@earendil-works/pi-coding-agent	Interactive coding agent CLI
@earendil-works/pi-tui	Terminal UI library with differential rendering

For Slack/chat automation and workflows see earendil-works/pi-chat.

Contributing

See CONTRIBUTING.md for contribution guidelines and AGENTS.md for project-specific rules (for both humans and agents).

Development

npm install --ignore-scripts  # Install all dependencies without running lifecycle scripts
npm run build        # Build all packages
npm run check        # Lint, format, and type check
./test.sh            # Run tests (skips LLM-dependent tests without API keys)
./pi-test.sh         # Run pi from sources (can be run from any directory)

Supply-chain hardening

We treat npm dependency changes as reviewed code changes.

• Direct external dependencies are pinned to exact versions. Internal workspace packages remain version-ranged.
• .npmrc sets save-exact=true and min-release-age=2 to avoid same-day dependency releases during npm resolution.
• package-lock.json is the dependency ground truth. Pre-commit blocks accidental lockfile commits unless PI_ALLOW_LOCKFILE_CHANGE=1 is set.
• npm run check verifies pinned direct deps, native TypeScript import compatibility, and the generated coding-agent shrinkwrap.
• The published CLI package includes packages/coding-agent/npm-shrinkwrap.json, generated from the root lockfile, to pin transitive deps for npm users.
• Release smoke tests use npm run release:local to build, pack, and create isolated npm and Bun installs outside the repo before publishing.
• Local release installs, documented npm installs, and pi update --self use --ignore-scripts where supported.
• CI installs with npm ci --ignore-scripts, and a scheduled GitHub workflow runs npm audit --omit=dev plus npm audit signatures --omit=dev.
• Shrinkwrap generation has an explicit allowlist for dependency lifecycle scripts; new lifecycle-script deps fail checks until reviewed.

License

MIT