`Travel Hacking Toolkit`: AI trip planning with skills + MCP

// related

• #0001

  #0001Agents & toolsClaude Code Releases1 hour ago

  `Claude Code` `v2.1.146` tightens code review and background sessions

  50radar

  Claude CodeTerminal coding agent — automates code edits with Claude

  Small release, but it removes several annoying agent-run failures. Windows, MCP pagination, and multi-agent env handling all get more reliable.

  • —/simplify is now /code-review with optional effort levels like high, making review intent clearer in repeatable workflows.
  • —MCP resources/list, resources/templates/list, and prompts/list no longer drop results after page 1. Tooling backed by large MCP servers becomes safer.
  • —Windows fixes cover pwsh launch failures, terminal strobing, NTFS junction cleanup, and GNOME paste behavior. Cross-platform CLI friction drops.
  • —CLAUDE_CODE_SUBAGENT_MODEL now reaches child processes in multi-agent sessions. Model routing gets less brittle for delegated coding runs.
  • —Auto-updater retries transient network failures, and large diff rendering is faster. Not flashy, but daily-use reliability improved.

  Source: github.com/anthropics/claude-code/releases/tag/v2.1.146Read original →
• #0002

  #0002Agents & toolsGeekNews3 hours ago

  Google Cloud revamps agent development with `Antigravity 2.0`

  70radar

  AntigravityAgent dev tool — links local prototypes to cloud execution

  Google is packaging local prototyping and cloud deployment into one agent stack. If Managed Agents API removes hosting glue, it is worth tracking now.

  • —Antigravity 2.0 and Managed Agents API are framed as an integrated dev kit, not separate demos.
  • —The flow targets local prototyping first, then managed cloud execution. Less custom orchestration if the API is usable.
  • —The available text is short, so pricing, lock-in, and runtime limits remain unknown. Treat it as watchlist, not migration trigger.

  Source: news.hada.io/topic?id=29718Read original →
• #0003

  #0003Agents & toolsr/ClaudeAI4 hours ago

  Rules for running phone-first vibe coding with `Claude Code`

  50radar

  Claude CodeAI coding agent — automates terminal-based code edits

  The useful part is the operating system: plan review, scoped chunks, commits, tests, and backups. Treat agents like junior implementers with guardrails, not magic.

  • —Plan mode is the control point. Bad decisions compound, so unclear sections should be challenged before code changes begin.
  • —If a plan cannot fit in your head, shrink the job. Smaller chunks reduce review burden and make rollback cleaner.
  • —After each completed plan, commit with git. It creates a code rollback point, but does not cover database state.
  • —Test cases should be readable in the plan: positives, negatives, missing inputs, and regressions before trusting generated code.
  • —For complex changes, use subagents for plan critique, security review, and testing audit; DB work needs backups first.

  Source: www.reddit.com/r/ClaudeAI/comments/1tj2i90/im_a_softwareRead original →