APX web admin lives local, but local is not auth. APC stays portable; APX still protects runtime routes. https://dev.to/agentprojectcontext/a-local-admin-panel-still-needs-auth-in-apx-4n1n https://github.com/agentprojectcontext/apx #opensource #ai

APC should stay durable and small. APX should assemble only needed context each turn, not dump the whole project. https://dev.to/agentprojectcontext/apx-should-assemble-context-not-dump-apc-into-every-prompt-3fid https://github.com/agentprojectcontext/apx #opensource #ai

I added ACP to APX without adding a second brain: one daemon, one stream, one adapter. Thin protocol surfaces keep the runtime easier to trust. #opensource #devtools #ai

APC migration means classify context: durable repo rules into .apc, sessions and secrets stay local. APX runs on top. https://dev.to/agentprojectcontext/apc-migration-should-classify-context-not-copy-folders-2m9i https://github.com/agentprojectcontext/agentprojectcontext #opensource #ai

APC Migration Should Classify Context, Not Copy Folders

Daily APC/APX post

dev.to

APC can travel with the repo, but runtimes do not. APX should detect installed CLIs before `apx run`. https://dev.to/agentprojectcontext/portable-context-does-not-mean-portable-runtimes-15pa https://github.com/agentprojectcontext/apx #opensource #ai

Keep AGENTS.md portable index; keep agent detail in .apc/agents. APC stays portable, APX stays practical. https://dev.to/agentprojectcontext/structured-agent-files-should-own-detail-agentsmd-should-stay-portable-4el9 https://github.com/agentprojectcontext/agentprojectcontext #opensource #ai

Structured Agent Files Should Own Detail. `AGENTS.md` Should Stay Portable.

Daily APC/APX post

dev.to

APX keeps unknown Telegram senders as guests until you assign a role. Safer bot trust by default. https://dev.to/agentprojectcontext/unknown-telegram-senders-should-stay-guests-in-apx-4lkl https://github.com/agentprojectcontext/apx #opensource #ai

APX keeps one core loop for CLI, web, desktop, and Telegram so APC context can travel without surface forks. https://dev.to/agentprojectcontext/apx-keeps-one-core-so-apc-can-reach-every-surface-15en https://github.com/agentprojectcontext/apx #opensource #ai

APX security_risk is not duplicate permission mode. It grades each action, so HIGH-risk calls can still stop. https://dev.to/agentprojectcontext/security-risk-grades-are-not-permission-modes-in-apx-m0f https://github.com/agentprojectcontext/apx #opensource #ai

APC/APX taught me a simple rule: docs are part of the contract, not cleanup. If EN and ES drift, or README gets ahead of code, the project tells two truths. I now edit docs like code and let the build catch drift. https://dev.to/tecnomanu/docs-are-part-of-the-contract-in-apc-and-apx-ebl

Routine definitions can live in APC, but routine memory should stay in APX runtime state. https://dev.to/agentprojectcontext/routine-memory-belongs-in-apx-not-apc-1e53 https://github.com/agentprojectcontext/apx #opensource #ai #devtools

Project MCP hints should name required env vars, not store secrets. APC stays portable; APX can audit and run safely. https://dev.to/agentprojectcontext/apc-mcp-hints-should-name-secrets-not-store-them-52pf https://github.com/agentprojectcontext/agentprojectcontext #opensource #ai #devtools

Descriptions should trigger loading, not store context. APC stays small; APX loads depth only when needed. https://dev.to/agentprojectcontext/descriptions-should-trigger-loading-not-store-context-35f6 https://github.com/agentprojectcontext/apx #opensource #ai #devtools

Project config arrays should replace, not merge. APC stays clear; APX runs exactly what this repo asked. https://dev.to/agentprojectcontext/project-config-arrays-should-replace-not-merge-1kji https://github.com/agentprojectcontext/apx #opensource #ai #devtools

Voice should layer onto APX surfaces, not become a fake channel. Cleaner prompts, logs, and UX. https://dev.to/agentprojectcontext/voice-is-a-mode-not-a-channel-16b7 https://github.com/agentprojectcontext/apx #ai #opensource #devtools

APX routines work best when they stay boring: `exec_agent` writes, shell ships, and `super_agent` only handles real orchestration. Clean boundary = easier retries, cleaner side effects. https://dev.to/tecnomanu/why-i-keep-apx-routines-boring-on-purpose-3ip8

"Super-agent" should stay a mode. APC names project agents; APX should show runtime identity, not a fake persona. https://dev.to/agentprojectcontext/super-agent-should-stay-a-mode-not-a-persona-1a4b https://github.com/agentprojectcontext/apx #opensource #ai #devtools

Project tasks belong in APX. APC should carry repo contract, while APX keeps daily task flow local and queryable. https://dev.to/agentprojectcontext/project-tasks-belong-in-apx-not-apc-268k https://github.com/agentprojectcontext/apx #opensource #ai

Weekend rabbit hole: how many people does it take to set off fireworks with each country's flag behind every World Cup match? 🎆 Environmental, legal, vendors — FIFA or the host? So I built the 2026 World Cup Operational Atlas with ChatGPT 5.6 (SOL). 👇 #WorldCup2026 #DataViz

I stopped treating the APX web admin as a separate product. It only works when it stays a thin browser surface over the same daemon and repo-owned state. New post: https://dev.to/tecnomanu/i-stopped-treating-the-web-admin-as-a-separate-product-4e93

Project config should travel with APC. APX should merge it with machine-local runtime settings, not hide it in one laptop. https://dev.to/agentprojectcontext/project-config-should-travel-with-apc-1g20 https://github.com/agentprojectcontext/apx #opensource #ai #devtools

Skill files can live in APC without bloating every prompt. APX should hint first and load bodies only when needed. https://dev.to/agentprojectcontext/skill-bodies-should-load-on-demand-2kj7 https://github.com/agentprojectcontext/apx #opensource #ai #devtools

Path-scoped rules belong in APC. APX keeps runtime state local and repo intent portable. https://dev.to/agentprojectcontext/path-scoped-rules-belong-in-apc-502g https://github.com/agentprojectcontext/agentprojectcontext #opensource #ai #devtools

Path-Scoped Rules Belong in APC

Daily APC/APX post

dev.to

Project skills should override global ones: APC keeps repo intent portable, APX adds local convenience. https://dev.to/agentprojectcontext/project-skills-should-override-global-skills-389o https://github.com/agentprojectcontext/apx #opensource #ai #devtools

You're not "a programmer". You're 1 of these 5 archetypes. Boris Cherny (creator of Claude Code) nails it: 🧪 Prototyper · 🏗️ Builder · 🧹 Sweeper · 📈 Grower · 🛠️ Maintainer Not job titles — ways of working. You switch depending on the day. Which one are you today? 👇

A stable project id keeps APC portable while APX keeps sessions, messages, and caches local. https://dev.to/agentprojectcontext/a-stable-project-id-keeps-apc-portable-and-apx-local-46ag https://github.com/agentprojectcontext/agentprojectcontext #opensource #ai #devtools

A Stable Project ID Keeps APC Portable and APX Local

Daily APC/APX post

dev.to

A good agent slug does more than name a role: it keeps APC definitions and APX runtime history aligned. https://dev.to/agentprojectcontext/agent-slugs-are-the-smallest-handoff-key-between-apc-and-apx-dom https://github.com/agentprojectcontext/apx #opensource #ai #devtools

Oops — this time the correct apx link 🙈 Install: npm install -g @agentprojectcontext/apx · repo: github.com/agentprojectcontext/apx

Not every memory belongs in APC. Curated project facts travel; APX keeps local runtime memory. https://dev.to/agentprojectcontext/not-every-memory-belongs-in-apc-3773 https://github.com/agentprojectcontext/apx #opensource #ai #devtools

My smart TV's internet was garbage. I described it to my agent like to a tech. 2-min diagnosis: not the ISP — the TV was on 2.4GHz wifi (300ms + packet loss). Moved it to 5GHz → 5ms. Then I asked for an app. It had Claude build one and sent me the link. 👇