Salesforce wants to move AI coding into a shared workspace with Slack Code

Salesforce now wants to put an AI coding agent directly into that workflow to reduce the number of handoffs and additional time involved in moving a software project from an idea to a finished product. The CRM software provider has released Slack Code, a.

The channel can retain relevant context from the conversation and give participants separate views for the agent’s conversation, its plan, code diffs, and the option to review the changes the agent makes, provide feedback and steer, pause or stop the agent if needed, Steigman.

What Happened

Salesforce’s bet is that allowing the stakeholders involved in a project to work alongside the same agent and intervene while it carries out a task can reduce the handoffs involved in moving the resulting code through subsequent stages of the development process..

• The service also comes with APIs that enterprises can use to tailor agent behavior and automate parts of the workflow, including account provisioning and authentication.

• For now, Salesforce said that agents operate within Slack’s existing permissions, security model and administrative controls.

• Otherwise, adding someone to a channel could effectively become a way to grant code access, creating a potential privilege-escalation risk, Patel noted.

Key Details

The same model could also broaden who gets to initiate software development work, Jena said, allowing, for example, a product manager who spots a bug to tag an agent and watch it produce a first pass instead of filing a ticket and.

• While Jena said enterprises will need to determine what information an agent can access inside a live channel and whether that access is limited to a specific task, Patel cautioned that Slack channel membership.

• Security and access controls will also be critical factors, analysts pointed out.

• The question of which tasks belong in Slack is only one part of the enterprise adoption equation, however.

Why It Matters

Typically, in traditional workflows, the reasoning behind an agent’s work, including what it was asked to do and the plan it followed, may remain in a developer’s terminal session or across different tools, leaving engineers to reconstruct that context from the final.

• Multiplayer fits small, well-scoped, visual or cross-functional work.

• Refactors, debugging, performance work, anything touching a system, you have to hold in your head.

What Reports Say

Coverage of the story so far points to:

• Continued reporting by InfoWorld as more details emerge