Filter
Exclude
Time range
-
Near
the two-step coding workflow that changes how you think about LLMs: 1. use tools like opencode that support plan mode → it reads context, makes a plan 2. execute the plan with any model finding: for 80% of dev tasks, the plan does the heavy lifting — not the model's raw power this means: - cheap models good workflow ≈ expensive models - expensive models help most on greenfield builds, rebases, complex rewrites - for everything else: plan first, execute second, save tokens tools like opencode already have this built in. worth using. #LocalAI #BuildInPublic #CodingWorkflow
31
The Claude API and Claude Code are architecturally different tools. The gap is larger than most developers think. I run a personal AI system with custom instructions (CLAUDE.md), MCP servers, and a context-routed knowledge base. When I needed programmatic access to all of it, I discovered three layers with very different capabilities. (1) The raw Claude API (Messages API) is stateless inference with limited built-in tooling. It has server-side web search and a text editor schema, but no bash execution, no file read/write execution, no agentic loop for client tools, no project context, and no MCP client. For anything beyond web search, you build the tool execution loop, the session layer, and the integrations yourself. (2) Claude Code is an agent runtime on top of the API. It adds 30 built-in tools (file ops, bash, grep, web search, subagents), automatic CLAUDE.md loading, a hook system with 23 event types, native MCP integration, session persistence, and an agentic loop that handles tool calling automatically. These are not cosmetic additions - they are the difference between a language model and a development agent. (3) The Claude Agent SDK sits between the two. Built-in tools and auto agentic loop like Claude Code, plus MCP and subagent support. But it defaults to isolation mode - CLAUDE.md loading requires explicit settingSources configuration. Different trade-off: more programmatic control, less automatic context. (4) To expose Claude Code's environment via HTTP, you can use CLI wrappers - tools that spawn claude -p (headless mode) behind an OpenAI-compatible API. Headless mode inherits CLAUDE.md, MCP servers, auto memory, environment variables, and all 30 tools automatically. Important caveat: hooks do not fire in headless mode, and skills (slash commands) are not available. You get the context and tools, but not the lifecycle automation layer. (5) I evaluated 8 open-source repos that do this. After checking the actual source code, feature coverage varies more than READMEs suggest. Repos worth tracking: - thhuang/claude-max-api-proxy-rs (Rust) - RichardAtCT/claude-code-openai-wrapper (Python) - codingworkflow/claude-code-api (Python) - CaddyGlow/ccproxy-api (Python) - ZhangHanDong/claude-code-api-rs (Rust) (6) The architectural decision that matters most: CLI wrappers vs SDK wrappers. CLI wrappers inherit CLAUDE.md and MCP for free because the CLI loads them. SDK wrappers need explicit setup but offer more programmatic control. Neither gives you hooks in headless mode - that remains an open gap. (7) The capability distance between the Claude API and Claude Code will keep growing as Anthropic adds agent features. Tools that bridge this gap programmatically are infrastructure worth watching.
2
2
13
751
Top 10 Developer Productivity Tools Every Software Engineer Must Be Aware of in 2026 #programming #software [ Source: ift.tt/B09wjod ] #rswebsols #DeveloperTools2026 #ProductivityHacks #SoftwareEngineering #AIAssistTools #CodingWorkflow
7
What's the best way to deploy llama 3 8b for faster inference
24
Replying to @CodingWorkflow
its packaged up with some helpful rules, pre-made codex prompts and some other nice-to-haves that make it better than just raw dogging the mcp
453
📢 NEWS ALERT 📢 Real Python’s Cursor Guide Lands at the Perfect Time: How Dev Leads Should Evaluate AI Editors and Set Guardrails. Real Python just shipped a hands-on Cursor guide, and it matters because teams are moving from “try Copilot” to “standardize an AI workflow.” This post breaks down what’s different about editor-level AI, how to evaluate Cursor vs plugins, and the practical guardrails that keep speed from turning into chaos. @realpython @cursor_ai 🔗 Tap below to dive deep into it 👇 bytebrief.vercel.app/blog/re… #CursorAI #AICoding #AIinDevelopment #AgenticCoding #PythonDevelopment #RealPython #AICodeEditor #DeveloperTools #CodingWorkflow #FutureOfCoding #VSCode #ProductivityBoost
1
2
37
VS Code shortcuts (Part 2). Window management. File handling. Small shortcuts → big speed boost. Save this 🔖 Follow for tech, crypto & science — simplified. #vscode #codingworkflow #developerlife #codingtips #learntech #deetechwiz
1
34
Have not seen code wiki yet. Will take a look. Thanks. I just stumbled on zread yesterday and it's kind of mind blowing indeed 🤯.
46
DeepWiki is quite amazing honestly.
1
72
26 Dec 2025
Replying to @CodingWorkflow
Actually I would say it mostly hurts speed, if you want high quality quants you need to do extra math during runtime. I think the speed gain is mostly because it can run all on gpu because it's smaller. I could be wrong.
403
Replying to @CodingWorkflow
Note «easy onboarding»
55
Day 34 Sometimes you get tired of building in public,sharing your views out in public and it's okay to be tired but we must keep on moving #CSS #htmlprojects #Coding #css3 #codingworkflow
11
Slow compared to what? This is ChatGPT speed.
40
19 Dec 2025
Replying to @CodingWorkflow
This is true, but breaking it down even further in an X post makes everything more confusing. It's stuff for a blog post or article. Anyway, I agree.
24