iamkrystian17

3 ms·

1.
by iamkrystian17 8mo ago
The containerized approach sounds interesting, I would definitely check it out
2.
by iamkrystian17 8mo ago
Where do you store your Claude/GPT skills? Inside .codex/.claude? If so you could tell them to put it under .ai/skills and lnai would symlinked them to .codex/.claude configs. Single source of truth
3.
by iamkrystian17 8mo ago
It is not really an agent package manager. It is a tool to sync agents configs. I checked out agent-resources, cool idea, maybe if lnai gains some traction I could contribut to your tool so it supports importing skills to .ai/ :)
4.
by iamkrystian17 8mo ago
Agents.md is usually only a part of ai coding tool config. LNAI handles syncing additional configs like skills, sub-dir rules, mcps, permissions to every tool. Additionally, even thought AGENTS.md is popular, not every tool supports that st
5.
by iamkrystian17 8mo ago
Yup with simple AGENTS file and skills, tools like ruler/lnai might be an overkill. However I still think that they are needed for MCPs/Permissions/sub-dir rules/different skills formats. I would really like all AI agent
6.
by iamkrystian17 8mo ago
At a glance there are a few differences: - LNAI additionally supports permissions - The way rules for sub-directories are defined is different. Ruler defines rules for sub-directories in the sub-directories themselves under ‘.ruler/‘.
7.
by iamkrystian17 8mo ago
Fair point. LNAI does support per-tool config overrides in .ai/.{codex/claude/cursor/etc.} directories, so you kind of get the best of both worlds :) You can sync identical configs, while having the flexibility to define
8.
by iamkrystian17 8mo ago
For simple config files like AGENTS.md/skills that is true. But some configs like MCPs/Permissions/Rules require transformations per tool. On lnai's per-tool docs pages (e.g. https://lnai.sh/tools/co
9.
by iamkrystian17 8mo ago
Totally valid take. Models might have different prompting guidelines for best results. If a developer uses one tool and wants to optimize their config as much as possible for that specific tool, LNAI is probably not for them. However given
10.
by iamkrystian17 8mo ago
For files that don't need transformation (AGENTS.md, skills, most rules), LNAI creates symlinks. .claude/CLAUDE.md → ../.ai/AGENTS.md. Edit the source, all tools see it immediately. For transformed files (Cursor's .
11.
by iamkrystian17 8mo ago
Yes, the tool takes that into account and transforms mcps/permissions/rules to different tool formats. Sadly some tools might not support fine-grained permissions (e.g. Codex) in which case a warning will be displayed but everythi
12.
LNAI – Define AI coding tool configs once, sync to Claude, Cursor, Codex, etc.(github.com)
70 points by iamkrystian17 8mo ago|30 comments
13.
by iamkrystian17 8mo ago
I've been using Claude Code, Cursor, and Codex on the same projects. Each tool has its own config format: Claude wants `.claude/`, Cursor wants `.cursor/`, Codex wants `.codex/`. Every time I updated a skill/rule, I