terminal
howtonotcode.com
Slack logo

Slack

Platform

Slack is a collaboration platform for team communication and efficiency.

article 4 storys calendar_today First seen: 2026-02-03 update Last seen: 2026-02-20 open_in_new Website menu_book Wikipedia

Resources

Links to check for updates: homepage, feed, or git repo.

home Homepage

Stories

Showing 1-4 of 4

ChatOps via Viktor AI in Slack: run workflows, create issues, manage tools

A new Viktor AI coworker for Slack promises chat-driven automation to run workflows, create issues, and manage tools directly from channels and DMs. Positioned as a ChatOps layer, the [Viktor AI coworker in Slack](https://app.alphasignal.ai/c?uid=VRJAfkRsPsudnEDm&cid=3e4916fed21fa79e&lid=qRQu9fCnTHrQU8He) aims to let teams trigger predefined workflows, open issues in their trackers, and perform common tool actions without leaving Slack. For backend and data teams, this can centralize routine ops (deploys, data jobs, on-call triage) behind secure, auditable chat commands. Start with narrow, high-signal automations (e.g., status checks, job restarts, issue templates) and progressively expand as permissions, observability, and failure handling prove reliable, using Slack as the shared control plane.

calendar_today 2026-02-20
viktor-ai slack chatops workflow-automation ai-assistant

Collab-first AI IDEs: Dropstone's Share Chat vs single-player agents

Collaborative AI coding workspaces like Dropstone’s Share Chat are challenging single‑user AI IDEs by letting PMs and engineers co-edit live contexts to push production-grade changes faster while preserving review control. [Dropstone’s Share Chat 3.0.5](https://medium.com/@epicprogrammer/the-23-minute-feature-how-dropstones-share-chat-is-breaking-the-ai-coding-hierarchy-9d6e4f93b303)[^1] contrasts with single-player agents by sharing a live reasoning+code state for real-time review/edits, targeting the “70% wall.” A practitioner comparison highlights day-to-day tradeoffs of [Cursor, Windsurf, and Claude Code](https://www.reddit.com/r/ClaudeCode/comments/1qzkwav/i_spent_the_last_month_rotating_between_windsurf/)[^2] [^1]: Adds: Explains Share Chat 3.0.5, live workspace links, and the “70% wall” with a concrete end-to-end example and workflow details. [^2]: Adds: Hands-on pros/cons and pricing context across Cursor, Windsurf, and Claude Code, including model access and collaboration features.

calendar_today 2026-02-09
dropstone blankline cursor windsurf claude-code

Claude Code 2.1.x lands practical speedups and governed multi‑agent workflows

Anthropic pushed a rapid series of Claude Code 2.1 updates (v2.1.26–v2.1.31) that cut RAM on session resume, add page‑level PDF reads, support MCP servers without dynamic registration, enable PR‑based session bootstraps, and ship many reliability fixes [Reddit summary](https://www.reddit.com/r/ClaudeAI/comments/1qvgdc5/claude_code_v21262130_what_changed/)[^1] and [official v2.1.31 notes](https://github.com/anthropics/claude-code/releases/tag/v2.1.31)[^2]. Practitioners also highlight 2.1’s skill hot‑reload, lifecycle hooks, and forked sub‑agents as a foundation for governed, observable multi‑agent workflows—positioning Claude Code as a lightweight "agent OS" for real projects [deep dive](https://medium.com/@richardhightower/build-agent-skills-faster-with-claude-code-2-1-release-6d821d5b8179)[^3]. [^1]: Adds: community changelog for v2.1.26–30 covering performance, MCP, GitHub/PR workflows, and PDF handling. [^2]: Adds: official v2.1.31 fixes (PDF lockups, sandbox FS errors, streaming temperature override, tool routing prompts, provider labels) and hard limits (100 pages, 20MB). [^3]: Adds: perspective on skill hot‑reload, lifecycle hooks, and forked sub‑agents enabling governed multi‑agent patterns.

calendar_today 2026-02-04
claude-code anthropic mcp-model-context-protocol github slack

CORE: Persistent memory and actions for coding agents via MCP

CORE is an open-source, self-hostable memory agent that gives coding assistants persistent, contextual recall of preferences, decisions, directives, and goals, and can trigger actions across your stack via MCP and app integrations like Linear, GitHub, Slack, Gmail, and Google Sheets; see [CORE on GitHub](https://github.com/RedPlanetHQ/core)[^1]. For backend/data teams, this replaces brittle context-dumps with time- and intent-aware retrieval across Claude Code and Cursor, enabling consistent code reviews and automated updates tied to prior decisions. [^1]: Adds: repo, docs, and integration details (MCP, supported apps, memory model, self-hosting).

calendar_today 2026-02-03
core redplanethq claude-code cursor mcp