AiHummer
English▾
Sign inAccount
v1.6.x▾
{ }Swagger

Project work, terminals and language navigation

v1.6.x · updated 2026-11-15

Development tools operate in the selected authorized project. An IDE connection, terminal or file reference does not give the agent the entire computer. Before starting, identify the project, intended change and how its result will be checked.

Interactive processes

For a program requiring sequential input, the agent can open a managed terminal session. For example, ask it to start an existing local tool, read its prompt, supply an answer and verify termination. Later input, reads and resize actions address that same session rather than starting the command again.

The session remains bound to its original user, agent and project. Cancellation must stop its owned process and wait for it to exit. Disconnecting the interface does not prove termination. After a restart, retained conversation history does not mean the old process was restored. Inspect an uncertain command outcome before executing another command that might repeat it.

When the administrator has configured the supported Go language server and matching SDK, ask the agent to find definitions, references or implementations, or show symbol information. Identify the current file and position. Reads use current document versions and Unicode positions; an old position reference requires fresh validation.

The language server sees only the authorized project and explicitly prepared public SDK. It does not receive sibling workspaces or a shared private module cache. Missing dependencies are not downloaded automatically. An unavailable server or incomplete index is reported as a limitation; an empty list does not prove that no references exist.

Implement and verify a change

A skill helps organize specification, planning, implementation, any migration, verification and review. It grants no command or file-write permission. Check the current contract for a new API. For interfaces, use the existing component catalogue and supported variants instead of inventing another similar control.

Before accepting a change, exercise the affected user flow, invalid input and recovery. Successful compilation does not replace behavior checks. A screenshot of a closed interface does not verify its open menu, focus or IME input. The result should state what was actually checked and the concrete limitations remaining.

Use the Runtime SDK and ACP to connect an IDE to the same Core conversation. Workspace permissions and tool approvals remain configured in Core independently of the client protocol.